Receber por email
← Voltar para o catálogo

workflow-feature-development

Complete workflow for developing new features from design to deployment. Use when starting a new feature, adding functionality, or building something new.

15estrelas
Atualizado há 4 meses

Ver no GitHub ↗ Licença: MIT

Como adicionar

/plugin marketplace add NickCrew/Claude-Cortex

O comando exato pode variar conforme o repositório. Confira o README no GitHub.

Para o autor da skill

Cole no README do seu repo

Mostra que sua skill está catalogada na Skillteca, gera backlink e tráfego rastreável.

[![Skillteca](https://www.skillteca.com.br/api/badge/workflow-feature-development/svg)](https://www.skillteca.com.br/skills/workflow-feature-development)

Alerta por categoria

Receba novas skills de Design e Frontend toda segunda

1 email curto, só com as skills novas de Design e Frontend. 4 minutos de leitura, sem spam, cancela com 1 clique.

Você confirma o email no primeiro envio. Sem spam. Cancela com 1 clique.

Ler descrição completa

Feature Development Workflow

Step-by-step process for developing features properly.

Phase 1: Design

Agents: system-architect

  • Design feature architecture
  • Identify components and boundaries
  • Define API contracts
  • Document data flow

Output: Architecture diagram, component list, API contracts

Phase 2: Planning

Agents: requirements-analyst

  • Break down into implementable tasks
  • Identify dependencies
  • Estimate timeline
  • Define acceptance criteria

Output: Task breakdown, dependency graph, timeline

Phase 3: Implementation

  • Implement feature following architecture
  • Work in small, testable increments
  • Commit frequently with clear messages

Phase 4: Review

Agents: code-reviewer, security-auditor

  • Code review for quality and standards
  • Security review for vulnerabilities
  • Focus: auth, input validation, data access

Blocking: Must pass before proceeding

Phase 5: Testing

Agents: test-automator

  • Unit tests (80% coverage target)
  • Integration tests
  • E2E tests for critical paths

Phase 6: Performance

Agents: performance-engineer

Validate against thresholds:

  • Response time: <200ms
  • Memory usage: <100MB
  • Bundle size: <500KB

Phase 7: Documentation

Agents: technical-writer

  • API documentation
  • User guide updates
  • Changelog entry

Phase 8: Deployment Prep

Agents: deployment-engineer

Checklist:

  • [ ] Version bump
  • [ ] Changelog updated
  • [ ] Migration scripts ready
  • [ ] Rollback plan documented

Success Criteria

  • [ ] All tests pass
  • [ ] Security scan clean
  • [ ] Performance within limits
  • [ ] Documentation complete

Rollback Plan

  1. Revert database migrations
  2. Restore previous version
  3. Notify stakeholders
Compartilhar X LinkedIn