implement
Start the implementation phase of a feature based on the approved plan.
12 stars
Best use case
implement is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Start the implementation phase of a feature based on the approved plan.
Teams using implement 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
$curl -o ~/.claude/skills/implement/SKILL.md --create-dirs "https://raw.githubusercontent.com/lionbenjamin/agent-templates/main/skills/implement/SKILL.md"
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/implement/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How implement Compares
| Feature / Agent | implement | 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?
Start the implementation phase of a feature based on the approved plan.
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.
SKILL.md Source
# Implement Skill Execute implementation plans with engineering excellence. ## When to Activate This skill is relevant when: - Implementing features from approved plans - Writing production code - Following technical designs - Executing task breakdowns ## Core Principles ### Clean Code - Self-documenting code - Small, focused functions - Clear naming conventions - Readable and maintainable ### TDD Discipline - Tests first whenever possible - Forces better design - Catches issues early - Living documentation ### Strict Adherence - Follow the plan - If plan is wrong, fix the plan first - Don't wing it - Ask when unclear ### SOLID Principles - Single Responsibility - Open/Closed - Liskov Substitution - Interface Segregation - Dependency Inversion ## Quick Checks When implementing, verify: - [ ] Following the approved plan - [ ] Writing tests first (TDD) - [ ] Code is clean and readable - [ ] Functions are small and focused - [ ] Names are clear and descriptive - [ ] Integration points verified - [ ] Library exports verified (don't guess) - [ ] Feature parity maintained during refactoring - [ ] No subtle features removed - [ ] Query filtering preserved - [ ] Optional params handled - [ ] Tests updated atomically with code - [ ] No syntax errors - [ ] Build passes - [ ] Existing patterns followed - [ ] Documentation updated
Related Skills
We are still matching the closest adjacent skills for this page. In the meantime, continue through the full directory.