Automated summary
Generates implementation plan documents by picking one of three complexity-tiered templates and saving a timestamped markdown file under docs/plans.
Strengths
- Explicit complexity-to-template mapping backed by concrete selection criteria
- Requires traceable detail: file paths with line numbers, external doc URLs, and acceptance criteria
- Conditional sections add design-system or infrastructure context only when the feature actually needs it
- Anti-pattern table steers away from over-planning obvious, localized changes
Limitations
- Relies on resources/minimal.md, standard.md and comprehensive.md, which are not included in this SKILL.md
- Acceptance criteria are described as coming from "blueprint Step 2", so standalone use means sourcing them yourself
- Does not validate the resulting plan or connect it to any issue tracker or task tooling
Use it when you need a written implementation plan for a bug fix, feature, or architectural change before writing code.
Skip it for a trivial one-line change you can just make, or when your team already mandates a different planning format.
Security analysis
SafeThe skill only uses Read, Write, and Edit to create planning documents under docs/plans. It does not execute commands, access networks, exfiltrate data, or modify unrelated files. Referenced resource templates are read-only inputs and pose no execution risk.
No concerns found
How this analysis is madeExamples
Write a minimal implementation plan for fixing the null pointer in src/auth/session.ts when the token expires, including acceptance criteria.Create a standard implementation plan for adding CSV export to the reports page: list the files I'll need to touch, any docs worth referencing, and testable acceptance criteria.Draft a comprehensive multi-phase plan for moving our Postgres setup to a multi-tenant schema, with risks, architectural decisions, and an infrastructure context section for our Terraform stack.name: plan-builder description: Write implementation plans with appropriate templates based on complexity. Provides minimal, standard, and comprehensive templates for different scope levels. allowed-tools: Read, Write, Edit
Plan Builder
Write implementation plans using the appropriate template based on complexity.
Template Selection
| Complexity | When to Use | Template |
|------------|-------------|----------|
| Minimal | Simple bugs, small improvements, clear single-file changes | resources/minimal.md |
| Standard | Most features, complex bugs, team collaboration | resources/standard.md |
| Comprehensive | Major features, architectural changes, multi-phase work | resources/comprehensive.md |
Selection Criteria
Use Minimal When
- Fix is obvious and localized
- Single file or 2-3 related files
- No architectural decisions needed
- Clear acceptance criteria from description
Use Standard When (Default)
- Multiple components affected
- Requires research or external docs
- Team needs context for review
- Has dependencies or risks
Use Comprehensive When
- New system or major feature
- Multiple phases of work
- Architectural decisions required
- Cross-cutting concerns (security, performance)
- Involves multiple teams or stakeholders
Plan Output
Write plans to: docs/plans/[YYYYMMDDHHMMSS]_<title>.md
Include in every plan:
- Research findings with file paths (e.g.,
src/models/user.rb:42) - External documentation URLs
- Related issues/PRs if known
- Acceptance Criteria from user input (populated from blueprint Step 2)
Conditional Sections
UI Features
Include "Design System Reference" section when feature involves:
- Pages, components, forms, buttons, modals
- Visual design elements
DevOps Features
Include "Infrastructure Context" section when feature involves:
- Terraform/OpenTofu, Ansible, cloud resources
- Docker, CI/CD, infrastructure
Anti-Patterns
| Don't | Do | |-------|-----| | Use comprehensive for simple bugs | Match template to actual complexity | | Skip Acceptance Criteria | Always include testable criteria | | Leave placeholder text | Fill all sections or remove them | | Over-plan obvious changes | Minimal template exists for a reason |
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/implementation-plan-builder-mmh8qqpi/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/implementation-plan-builder-mmh8qqpi' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/implementation-plan-builder-mmh8qqpi/download' --output '.skill-downloads/implementation-plan-builder-mmh8qqpi/SKILL.md.part' && mv '.skill-downloads/implementation-plan-builder-mmh8qqpi/SKILL.md.part' '.skill-downloads/implementation-plan-builder-mmh8qqpi/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
Tools declared by the author (check availability in your agent): Read, Write, Edit
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
Claude Code
test -f '.skill-downloads/implementation-plan-builder-mmh8qqpi/SKILL.md' && test -s '.skill-downloads/implementation-plan-builder-mmh8qqpi/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/plan-builder' && cp -R '.skill-downloads/implementation-plan-builder-mmh8qqpi' '.claude/skills/plan-builder'OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/implementation-plan-builder-mmh8qqpi'openskills read 'implementation-plan-builder-mmh8qqpi'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/implementation-plan-builder-mmh8qqpi/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
Supabase Docs Authoring
Documentation
Write, edit, and review Supabase documentation content including guides, tutorials, reference docs, and partials. Follow style guides and MDX/TOML validation rules.
Create Architecture Decision Record
Documentation
Create a new Architecture Decision Record with sequential numbering, register it in the AgentDB graph, and link related ADRs.
Plan update with deep research
Documentation
Updates a plan document by launching parallel subagents to analyze a topic across all compiler passes, then consolidates findings into the plan doc.