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.
What this skill does
# 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 <[email protected]>"
# 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 "- ImplRelated in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context โ no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes โ information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development โ guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.