implementation
Use when implementing features from feature-list.json, writing code following project patterns, or using MCP tools efficiently. Load in IMPLEMENT state. Covers coding patterns, test writing, health checks, and token-efficient MCP usage (defer_loading for 85% savings).
When & Why to Use This Skill
This Claude skill streamlines the software development lifecycle by automating feature implementation, ensuring strict adherence to project-specific coding patterns, and optimizing MCP tool usage for maximum token efficiency. It provides a structured framework for transitioning from task requirements to verified, production-ready code through integrated testing and automated health check protocols.
Use Cases
- Feature Development: Automatically implement new functionalities from a feature-list.json while maintaining consistency with existing project architectures and reference patterns.
- Automated QA & Verification: Generate unit tests concurrently with code implementation and execute health-check scripts to ensure system stability and code quality.
- Token-Optimized MCP Integration: Efficiently utilize Model Context Protocol tools with advanced strategies like 'defer_loading' to reduce token consumption by up to 85%.
- End-to-End Workflow Automation: Manage the complete development loop, including fetching current tasks, querying context graphs, performing implementation, and executing automated Git commits with feature-specific metadata.
| name | implementation |
|---|---|
| description | "Use when implementing features from feature-list.json, writing code following project patterns, or using MCP tools efficiently. Load in IMPLEMENT state. Covers coding patterns, test writing, health checks, and token-efficient MCP usage (defer_loading for 85% savings)." |
| keywords | implement, code, develop, mcp, patterns, health-check |
Implementation
Feature development for IMPLEMENT state.
Instructions
- Get current feature:
scripts/get-current-feature.sh - Query context graph for similar work
- Implement following project patterns (see references/)
- Write tests alongside code
- Run health check:
scripts/health-check.sh - Git commit:
scripts/feature-commit.sh <feature-id> - Mark complete:
scripts/mark-feature-complete.sh
Exit Criteria (Code Verified)
# All must pass
scripts/health-check.sh && echo "Health OK"
[ -f "tests/test_*.py" ] || [ -f "*.test.ts" ]
[ -z "$(git status --porcelain)" ] && echo "Changes committed"
jq '.features[] | select(.id=="'$FEATURE_ID'") | .status == "implemented"' .claude/progress/feature-list.json
Scripts
| Script | Purpose |
|---|---|
scripts/feature-commit.sh |
Commit with feature ID message |
scripts/session-commit.sh |
Checkpoint commit at session end |
References
| File | Load When |
|---|---|
| references/coding-patterns.md | Writing implementation code |
| references/mcp-usage.md | Using MCP tools efficiently |
| references/health-checks.md | Verifying implementation |
| references/async-parallel-operations.md | Running independent operations in parallel |