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.
Best use case
workflow-feature-development is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Complete workflow for developing new features from design to deployment. Use when starting a new feature, adding functionality, or building something new.
Teams using workflow-feature-development should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/workflow-feature-development/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How workflow-feature-development Compares
| Feature / Agent | workflow-feature-development | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Complete workflow for developing new features from design to deployment. Use when starting a new feature, adding functionality, or building something new.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
SKILL.md Source
# 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
Related Skills
workflow-security-audit
Comprehensive security assessment and remediation. Use for security reviews, compliance checks, vulnerability assessments.
workflow-performance
Systematic performance analysis and optimization. Use when things are slow, need optimization, or preparing for scale.
workflow-feature
Complete feature development workflow from design to deployment. Use when implementing new features or functionality.
workflow-bug-fix
Systematic approach to identifying, fixing, and validating bug fixes. Use when fixing bugs, resolving issues, or addressing errors.
test-driven-development
Use when implementing any feature or bugfix, before writing implementation code - write the test first, watch it fail, write minimal code to pass; ensures tests actually verify behavior by requiring failure first
subagent-driven-development
Use when executing implementation plans with independent tasks in the current session - dispatches fresh subagent for each task with code review between tasks, enabling fast iteration with quality gates
implementation-workflow
Use when turning PRDs or feature specs into actionable implementation workflows - provides structured task decomposition, dependency mapping, and validation gates.
gitops-workflows
GitOps workflows and patterns using ArgoCD and Flux for declarative Kubernetes deployments. Use when implementing CI/CD for Kubernetes, managing multi-environment deployments, or adopting declarative infrastructure practices.
github-actions-workflows
GitHub Actions workflow patterns for CI/CD including matrix builds, reusable workflows, secrets management, and caching strategies. Use when setting up or optimizing GitHub Actions pipelines.
finishing-a-development-branch
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup
feature-implementation
Use when implementing a feature or multi-file code change - provides structured implementation flow with persona selection, validation, and testing guidance.
development-estimation
Use when estimating time, effort, or complexity for features or projects - provides structured estimation workflows with breakdowns, risks, and confidence intervals.