feature-dev-complete
Complete feature development lifecycle from research to deployment. Uses Gemini Search for best practices, architecture design, Codex prototyping, comprehensive testing, and documentation generation. Full 12-stage workflow.
Best use case
feature-dev-complete is best used when you need a repeatable AI agent workflow instead of a one-off prompt. It is especially useful for teams working in multi. Complete feature development lifecycle from research to deployment. Uses Gemini Search for best practices, architecture design, Codex prototyping, comprehensive testing, and documentation generation. Full 12-stage workflow.
Complete feature development lifecycle from research to deployment. Uses Gemini Search for best practices, architecture design, Codex prototyping, comprehensive testing, and documentation generation. Full 12-stage workflow.
Users should expect a more consistent workflow output, faster repeated execution, and less time spent rewriting prompts from scratch.
Practical example
Example input
Use the "feature-dev-complete" skill to help with this workflow task. Context: Complete feature development lifecycle from research to deployment. Uses Gemini Search for best practices, architecture design, Codex prototyping, comprehensive testing, and documentation generation. Full 12-stage workflow.
Example output
A structured workflow result with clearer steps, more consistent formatting, and an output that is easier to reuse in the next run.
When to use this skill
- Use this skill when you want a reusable workflow rather than writing the same prompt again and again.
When not to use this skill
- Do not use this when you only need a one-off answer and do not need a reusable workflow.
- Do not use it if you cannot install or maintain the related files, repository context, or supporting tools.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/feature-dev-complete/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How feature-dev-complete Compares
| Feature / Agent | feature-dev-complete | 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 feature development lifecycle from research to deployment. Uses Gemini Search for best practices, architecture design, Codex prototyping, comprehensive testing, and documentation generation. Full 12-stage workflow.
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
Cursor vs Codex for AI Workflows
Compare Cursor and Codex for AI coding workflows, repository assistance, debugging, refactoring, and reusable developer skills.
AI Agents for Coding
Browse AI agent skills for coding, debugging, testing, refactoring, code review, and developer workflows across Claude, Cursor, and Codex.
Best AI Skills for Claude
Explore the best AI skills for Claude and Claude Code across coding, research, workflow automation, documentation, and agent operations.
SKILL.md Source
# Feature Development Complete
## Purpose
Execute complete feature development lifecycle using multi-model AI orchestration.
## Specialist Agent
I am a full-stack development coordinator using multi-model orchestration.
**Methodology** (Complete Lifecycle Pattern):
1. Research best practices (Gemini Search)
2. Analyze existing patterns (Gemini MegaContext)
3. Design architecture (Claude Architect)
4. Generate diagrams (Gemini Media)
5. Rapid prototype (Codex Auto)
6. Comprehensive testing (Codex Iteration)
7. Style polish (Claude)
8. Documentation (Multi-model)
9. Performance optimization
10. Security review
11. Create PR with comprehensive report
12. Deploy readiness check
**Models Used**:
- **Gemini Search**: Latest best practices, framework updates
- **Gemini MegaContext**: Large codebase pattern analysis
- **Gemini Media**: Architecture diagrams, flow charts
- **Claude**: Architecture design, testing strategy
- **Codex**: Rapid prototyping, auto-fixing
- **All models**: Documentation generation
## Input Contract
```yaml
input:
feature_spec: string (feature description, required)
target_directory: string (default: src/)
create_pr: boolean (default: true)
deploy_after: boolean (default: false)
```
## Output Contract
```yaml
output:
artifacts:
research: markdown (best practices)
architecture: markdown (design doc)
diagrams: array[image] (visual docs)
implementation: directory (code)
tests: directory (test suite)
documentation: markdown (usage docs)
quality:
test_coverage: number (percentage)
quality_score: number (0-100)
security_issues: number
pr_url: string (if create_pr: true)
deployment_ready: boolean
```
## Execution Flow
```bash
#!/bin/bash
set -e
FEATURE_SPEC="$1"
TARGET_DIR="${2:-src/}"
OUTPUT_DIR="feature-$(date +%s)"
mkdir -p "$OUTPUT_DIR"
echo "================================================================"
echo "Complete Feature Development: $FEATURE_SPEC"
echo "================================================================"
# STAGE 1: Research Best Practices
echo "[1/12] Researching latest best practices..."
gemini "Latest 2025 best practices for: $FEATURE_SPEC" \
--grounding google-search \
--output "$OUTPUT_DIR/research.md"
# STAGE 2: Analyze Existing Codebase Patterns
echo "[2/12] Analyzing existing codebase patterns..."
LOC=$(find "$TARGET_DIR" -type f \( -name "*.js" -o -name "*.ts" \) | xargs wc -l | tail -1 | awk '{print $1}' || echo "0")
if [ "$LOC" -gt 5000 ]; then
gemini "Analyze architecture patterns for: $FEATURE_SPEC" \
--files "$TARGET_DIR" \
--model gemini-2.0-flash \
--output "$OUTPUT_DIR/codebase-analysis.md"
else
echo "Small codebase - skipping mega-context analysis"
fi
# STAGE 3: Initialize Development Swarm
echo "[3/12] Initializing development swarm..."
npx claude-flow coordination swarm-init \
--topology hierarchical \
--max-agents 6 \
--strategy balanced
# STAGE 4: Architecture Design
echo "[4/12] Designing architecture..."
# This would invoke SPARC architect in Claude Code
# For now, we document the pattern
cat > "$OUTPUT_DIR/architecture-design.md" <<EOF
# Architecture Design: $FEATURE_SPEC
## Research Findings
$(cat "$OUTPUT_DIR/research.md")
## Existing Patterns
$(cat "$OUTPUT_DIR/codebase-analysis.md" 2>/dev/null || echo "N/A")
## Proposed Architecture
[Generated by Claude Architect Agent]
## Design Decisions
[Key decisions with rationale]
EOF
# STAGE 5: Generate Architecture Diagrams
echo "[5/12] Generating architecture diagrams..."
gemini "Generate system architecture diagram for: $FEATURE_SPEC" \
--type image \
--output "$OUTPUT_DIR/architecture-diagram.png" \
--style technical
gemini "Generate data flow diagram for: $FEATURE_SPEC" \
--type image \
--output "$OUTPUT_DIR/data-flow.png" \
--style diagram
# STAGE 6: Rapid Prototyping
echo "[6/12] Rapid prototyping with Codex..."
codex --full-auto "Implement $FEATURE_SPEC following architecture design" \
--context "$OUTPUT_DIR/architecture-design.md" \
--context "$OUTPUT_DIR/research.md" \
--sandbox true \
--output "$OUTPUT_DIR/implementation/"
# STAGE 7: Theater Detection
echo "[7/12] Detecting placeholder code..."
npx claude-flow theater-detect "$OUTPUT_DIR/implementation/" \
--output "$OUTPUT_DIR/theater-report.json"
THEATER_COUNT=$(cat "$OUTPUT_DIR/theater-report.json" | jq '.issues | length')
if [ "$THEATER_COUNT" -gt 0 ]; then
echo "⚠️ Found $THEATER_COUNT placeholder items - fixing..."
# Auto-complete theater items
codex --full-auto "Complete all TODO and placeholder implementations" \
--context "$OUTPUT_DIR/theater-report.json" \
--context "$OUTPUT_DIR/implementation/" \
--sandbox true
fi
# STAGE 8: Comprehensive Testing with Codex Iteration
echo "[8/12] Testing with Codex auto-fix..."
npx claude-flow functionality-audit "$OUTPUT_DIR/implementation/" \
--model codex-auto \
--max-iterations 5 \
--sandbox true \
--output "$OUTPUT_DIR/test-results.json"
# STAGE 9: Style Audit & Polish
echo "[9/12] Polishing code quality..."
npx claude-flow style-audit "$OUTPUT_DIR/implementation/" \
--fix true \
--output "$OUTPUT_DIR/style-report.json"
# STAGE 10: Security Review
echo "[10/12] Security review..."
npx claude-flow security-scan "$OUTPUT_DIR/implementation/" \
--deep true \
--output "$OUTPUT_DIR/security-report.json"
SECURITY_CRITICAL=$(cat "$OUTPUT_DIR/security-report.json" | jq '.critical_issues')
if [ "$SECURITY_CRITICAL" -gt 0 ]; then
echo "🚨 Critical security issues found!"
cat "$OUTPUT_DIR/security-report.json" | jq '.critical_issues[]'
exit 1
fi
# STAGE 11: Documentation Generation
echo "[11/12] Generating documentation..."
cat > "$OUTPUT_DIR/FEATURE-DOCUMENTATION.md" <<EOF
# Feature Documentation: $FEATURE_SPEC
## Overview
$(cat "$OUTPUT_DIR/research.md" | head -10)
## Architecture

## Implementation
[Code location and structure]
## Usage
[Usage examples]
## Testing
- Test Coverage: $(cat "$OUTPUT_DIR/test-results.json" | jq '.coverage_percent')%
- Tests Passing: $(cat "$OUTPUT_DIR/test-results.json" | jq '.all_passed')
## Quality Metrics
- Quality Score: $(cat "$OUTPUT_DIR/style-report.json" | jq '.quality_score')/100
- Security Issues: 0 critical
---
🤖 Generated with Claude Code Complete Feature Development
EOF
# STAGE 12: Production Readiness Check
echo "[12/12] Final production readiness check..."
TESTS_PASSED=$(cat "$OUTPUT_DIR/test-results.json" | jq '.all_passed')
QUALITY_SCORE=$(cat "$OUTPUT_DIR/style-report.json" | jq '.quality_score')
SECURITY_OK=$([ "$SECURITY_CRITICAL" -eq 0 ] && echo "true" || echo "false")
if [ "$TESTS_PASSED" = "true" ] && [ "$QUALITY_SCORE" -ge 85 ] && [ "$SECURITY_OK" = "true" ]; then
echo "✅ Production ready!"
# Create PR if requested
if [ "${CREATE_PR:-true}" = "true" ]; then
echo "Creating pull request..."
# Copy implementation to target directory
cp -r "$OUTPUT_DIR/implementation/"* "$TARGET_DIR/"
# Git operations
git add .
git commit -m "feat: $FEATURE_SPEC
🤖 Generated with Claude Code Complete Feature Development
## Quality Metrics
- ✅ All tests passing
- ✅ Code quality: $QUALITY_SCORE/100
- ✅ Security: No critical issues
- ✅ Test coverage: $(cat "$OUTPUT_DIR/test-results.json" | jq '.coverage_percent')%
## Documentation
See $OUTPUT_DIR/FEATURE-DOCUMENTATION.md
Co-Authored-By: Claude <noreply@anthropic.com>"
# Create PR
gh pr create --title "feat: $FEATURE_SPEC" \
--body-file "$OUTPUT_DIR/FEATURE-DOCUMENTATION.md"
fi
else
echo "⚠️ Not production ready - review issues"
exit 1
fi
echo ""
echo "================================================================"
echo "Feature Development Complete!"
echo "================================================================"
echo ""
echo "Artifacts in: $OUTPUT_DIR/"
echo "- Research: research.md"
echo "- Architecture: architecture-design.md"
echo "- Diagrams: *.png"
echo "- Implementation: implementation/"
echo "- Tests: test-results.json"
echo "- Documentation: FEATURE-DOCUMENTATION.md"
echo ""
```
## Integration Points
### Cascades
- Standalone complete workflow
- Can be part of `/sprint-automation` cascade
- Used by `/feature-request-handler` cascade
### Commands
- Uses: `/gemini-search`, `/gemini-megacontext`, `/gemini-media`
- Uses: `/codex-auto`, `/functionality-audit`, `/style-audit`
- Uses: `/theater-detect`, `/security-scan`
- Uses: `/swarm-init`, `/auto-agent`
### Other Skills
- Invokes: `quick-quality-check`, `smart-bug-fix` (if issues found)
- Output to: `code-review-assistant`, `documentation-generator`
## Usage Example
```bash
# Develop complete feature
feature-dev-complete "User authentication with JWT and refresh tokens"
# Feature with custom target
feature-dev-complete "Payment processing integration" src/payments/
# Feature without PR
feature-dev-complete "Dark mode toggle" --create-pr false
```
## Failure Modes
- **Research insufficient**: Escalate to user for more context
- **Tests fail after iterations**: Manual intervention required
- **Security issues critical**: Block deployment, escalate
- **Quality score too low**: Run additional polish iterations
- **Architecture unclear**: Request user input on design decisionsRelated Skills
game-changing-features
Find 10x product opportunities and high-leverage improvements. Use when user wants strategic product thinking, mentions '10x', wants to find high-impact features, or says 'what would make this 10x better', 'product strategy', or 'what should we build next'.
full-stack-orchestration-full-stack-feature
Use when working with full stack orchestration full stack feature
data-engineering-data-driven-feature
Build features guided by data insights, A/B testing, and continuous measurement using specialized agents for analysis, implementation, and experimentation.
backend-development-feature-development
Orchestrate end-to-end backend feature development from requirements to deployment. Use when coordinating multi-phase feature delivery across teams and services.
screenshot-feature-extractor
Analyze product screenshots to extract feature lists and generate development task checklists. Use when: (1) Analyzing competitor product screenshots for feature extraction, (2) Generating PRD/task lists from UI designs, (3) Batch analyzing multiple app screens, (4) Conducting competitive analysis from visual references.
feature-design-assistant
Turn ideas into fully formed designs and specs through natural collaborative dialogue. Use when planning new features, designing architecture, or making significant changes to the codebase.
brainstorming-features
Facilitates creative ideation sessions for mobile and web app features, generating structured ideas with user stories, technical considerations, and implementation suggestions. Use when planning new features, exploring product direction, generating app ideas, feature discovery, product brainstorming, or when user mentions 'brainstorm', 'ideate', 'app ideas', or 'feature suggestions'.
agentdb-advanced-features
Master advanced AgentDB features including QUIC synchronization, multi-database management, custom distance metrics, hybrid search, and distributed systems integration. Use when building distributed AI systems, multi-agent coordination, or advanced vector search applications.
plan-feature
Plan a new feature with analysis, design, and implementation steps. Use when the user asks to plan a feature or run /plan-feature.
create-feature
新機能開発統合スキル - 要件分析からPR作成まで、新機能開発の全工程を自動化します。analyze-requirements、develop-backend、develop-frontend、review-architecture、qa-check、create-prの各専門スキルを適切な順序で呼び出し、完全な機能開発を実現します。品質基準(テストカバレッジ80%以上、Lint/ビルド成功)を満たすまで自動的にレビュー・修正を繰り返します。
rn-native-features
Native iOS features in Expo React Native apps. Use when implementing camera, push notifications, haptics, permissions, device sensors, or other native APIs in Expo.
feature-file
Manage features.yml for tracking requirements and progress; use proactively ONLY when features.yml already exists, or invoke manually to create one; complements TodoWrite for persistent project state.