plan
Create technical implementation plans from specifications. Uses TDD approach and defines clear verification strategy.
12 stars
Best use case
plan is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Create technical implementation plans from specifications. Uses TDD approach and defines clear verification strategy.
Teams using plan 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/plan/SKILL.md --create-dirs "https://raw.githubusercontent.com/lionbenjamin/agent-templates/main/skills/plan/SKILL.md"
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/plan/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How plan Compares
| Feature / Agent | plan | 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?
Create technical implementation plans from specifications. Uses TDD approach and defines clear verification strategy.
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
# Plan Skill Architect solutions with technical implementation plans. ## When to Activate This skill is relevant when: - Creating implementation plans from specs - Designing technical solutions - Planning database and code changes - Defining verification strategies ## Core Principles ### Scalability & Performance - Will this query scale? - Are patterns efficient? - Consider performance early - Plan for growth ### Data Integrity - Design schema for correctness - Use foreign keys and constraints - Choose appropriate types - Enforce data validation ### Future-Proofing - Is this extensible? - Avoid painting into corners - Consider evolution paths - Balance flexibility and simplicity ### Complexity Management - Keep it simple - Avoid over-engineering - Use appropriate patterns - Clear, maintainable design ### TDD Strategy - TDD Strategy section MUST come before Proposed Changes in every plan - List new test files to create, with specific test case names - List existing test files to update, with specific additions - For each test case, describe: input → expected output - Specify test commands to run (e.g. `npm test`, `pytest`) - State expected test count change (e.g. "+8 new tests") - In Proposed Changes, list test file changes before implementation file changes ### Accessibility Planning - Identify ARIA requirements early - Plan keyboard navigation - Consider screen readers - Design for all users ## Quick Checks When creating plans, verify: - [ ] TDD strategy section present with test files, test cases, and test commands - [ ] Test files listed BEFORE implementation files in Proposed Changes - [ ] All spec requirements covered - [ ] Database schema changes valid - [ ] Test cases specified before code - [ ] Accessibility requirements planned - [ ] Existing code patterns reviewed - [ ] Integration points identified - [ ] Verification plan is detailed - [ ] Manual and automated tests defined - [ ] Breaking changes documented - [ ] Migration strategy included - [ ] Rollback plan exists
Related Skills
We are still matching the closest adjacent skills for this page. In the meantime, continue through the full directory.