playbooks

home / skills / nickcrew / claude-cortex / workflow-feature-development

workflow-feature-development skill

/skills/workflow-feature-development

This skill guides end-to-end feature development from design to deployment, ensuring architecture, planning, testing, and documentation are aligned with

npx playbooks add skill nickcrew/claude-cortex --skill workflow-feature-development

Review the files below or copy the command above to add this skill to your agents.

Files (1)
SKILL.md
1.9 KB
---
name: workflow-feature-development
description: Complete workflow for developing new features from design to deployment. Use when starting a new feature, adding functionality, or building something new.
---

# 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

Overview

This skill provides a complete, repeatable workflow for developing new features from design through deployment. It formalizes phases, agent roles, and checkpoints to reduce risk and accelerate delivery. Use it to ensure consistent quality, security, and operational readiness for any new functionality.

How this skill works

The workflow breaks feature work into eight phases: Design, Planning, Implementation, Review, Testing, Performance, Documentation, and Deployment Prep. Each phase lists concrete outputs, responsible agent roles, and measurable criteria (tests, performance thresholds, security checks). A final success checklist and a rollback plan close the loop for safe releases.

When to use it

  • Starting a new feature or major enhancement
  • Adding cross-cutting functionality (auth, data access, APIs)
  • Planning a release that requires migrations or rollout coordination
  • When you need a reproducible, auditable development process for teams
  • Preparing features that must meet performance or security SLAs

Best practices

  • Design architecture first: define components, boundaries, and API contracts before coding
  • Break work into small, testable increments with clear acceptance criteria
  • Run mandatory code and security reviews; block merging until issues are resolved
  • Automate unit, integration, and E2E tests aiming for the coverage target
  • Validate performance against concrete thresholds and document results
  • Prepare deployment artifacts: version bump, changelog, migrations, and rollback plan

Example use cases

  • Build a new recommendation engine endpoint with defined API contracts and integration tests
  • Add role-based access to an existing service with security review and data migration plan
  • Ship a client-side feature with bundle size targets and performance verification
  • Release a database-backed feature requiring migration scripts and a documented rollback flow
  • Onboard a third-party integration with contract tests and operational runbook

FAQ

What are the concrete performance thresholds to validate?

Validate response time under 200ms, memory usage under 100MB, and bundle size under 500KB as baseline targets; adjust for product context.

What must pass before deployment?

All automated tests, a clean security scan, documented performance results within limits, completed documentation, and the deployment checklist items (version bump, changelog, migrations, rollback plan).