implementation-plan-creator
Create the implementation plan artifact from an approved task list
Best use case
implementation-plan-creator is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Create the implementation plan artifact from an approved task list
Teams using implementation-plan-creator 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
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/implementation-plan-creator/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How implementation-plan-creator Compares
| Feature / Agent | implementation-plan-creator | 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 the implementation plan artifact from an approved task list
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
You are creating the **Implementation Plan artifact** (`implementation-plan.md`) for an artifact-driven development workflow. ## Input Context - Read `.artifacts/bld-<project-slug>/todo.md` for the approved task list - Reference the conversation context for requirements and constraints ## Your Task Create `.artifacts/bld-<project-slug>/implementation-plan.md`. ## Plan Structure ### Project Summary One paragraph describing what's being built and its core purpose. ### User Review Required Surface decisions requiring user input **prominently at the top**. Use blockquote callouts: > **IMPORTANT** > **Technology Stack**: The plan uses X with Y. If you prefer Z, please let me know. > **IMPORTANT** > **[Decision Topic]**: The proposed approach uses [approach]. Alternative approaches include: > - Alternative 1 > - Alternative 2 > - Alternative 3 > > Please confirm the preferred approach. This section ensures approval gates are visible, not buried. ### Proposed Changes Organize by logical layer or area (Backend Service Layer, Frontend Components, Configuration, etc.). For each file: **[NEW]** `path/to/file.ext` Brief description of this file's purpose: - Responsibility one - Responsibility two - Responsibility three **[MODIFY]** `path/to/existing.ext` Changes to make: - Add X functionality - Update Y to support Z ### Testing Strategy How the implementation will be verified. Keep it practical—what tests or checks prove it works. ## Artifact Structure ```markdown --- status: pending created: <timestamp> updated: <timestamp> --- # <Project Name> <One paragraph project summary> ## User Review Required > **IMPORTANT** > **[Decision 1]**: ... > **IMPORTANT** > **[Decision 2]**: ... ## Proposed Changes ### <Layer/Area Name> **[NEW]** `filename.ext` Description: - Point one - Point two **[MODIFY]** `filename.ext` Changes: - Change one - Change two ### Testing Strategy ... ``` ## After Creation Present the artifact to the user. **This is an approval gate.** **When presenting**, always: 1. Show the file path at the top: `📄 .artifacts/bld-<project-slug>/implementation-plan.md` 2. If the document is reasonably sized, display the full markdown content 3. If the document is large, provide an overview and instruct the user: "See the full plan at the file path above." The "User Review Required" section makes explicit what needs confirmation. Do not proceed until: - All IMPORTANT items are addressed - User explicitly approves the approach Once approved, update `status: in-progress`. **IMPORTANT**: Every time you modify `implementation-plan.md`, update the `updated:` field in the frontmatter with the current timestamp.
Related Skills
walkthrough-creator
Create and maintain the walkthrough artifact during implementation
task-list-creator
Create or update the task list artifact from gathered requirements
feature-spec-creator
Generates a feature spec for an existing codebase via an interview workflow. Use when the user wants to write, draft, or scope a feature spec — phrases like "write a feature spec", "spec out this feature", "draft a spec for X", "I want to add X to this codebase", "let's plan a new feature", or "scope out this feature". Do NOT use for bug fixes, pure refactors with no behavior change, or greenfield projects with no existing code.
obsidian-cli
Use the Obsidian CLI to manage knowledge in an Obsidian vault — daily notes, search, tasks, tags, link graph analysis, properties, templates, and file operations. This skill should be used when the user asks to interact with their Obsidian vault, manage daily notes, search notes, manage tasks, explore tags or backlinks, set properties, use templates, or perform vault maintenance.
qr-code
Generate QR codes from URLs, text, or other data and save them as SVG, PNG, EPS, or PDF files. This skill should be used when the user asks to create, generate, or make a QR code for any content such as website URLs, text strings, WiFi credentials, contact info, or other data. Triggers include mentions of 'QR code', 'QR', 'barcode for a link', or requests to make a scannable code. Supports customization of colors, size, error correction level, and output format.
powerpoint
Create professional PowerPoint presentations. Use when asked to "create a PowerPoint", "make a presentation", "build slides", or generate pptx files.
pdf-ocr
Parse PDF files to markdown using GLM-OCR via Ollama locally. Converts each page to an image, runs OCR, and outputs clean markdown. Use when the user wants to extract text from a PDF.
ralph-method
Set up a Ralph Wiggum task - runs Phase 1 (requirements interview) and Phase 2 (implementation planning), then stops with instructions to run the building loop. Creates namespaced specs in specs/[task-name]/.
journal
An agent to journal developer activity over a specified time period.
adr-manager
Add Architecture Decision Record (ADR) entries to an ADR file. This skill should be used when recording significant architectural decisions during development. It handles formatting and appending entries using Michael Nygard's ADR template.
essay-draft-from-research
Produces a long-form essay draft grounded in a user-supplied directory of research documents via an interview workflow. Use whenever the user wants to "draft an essay from my research", "write an essay from these notes", "turn this research directory into an essay", "I've been collecting notes on X, help me draft an essay", or "draft a long-form piece using these sources". Do NOT use for: one-shot summarization of a single document, short notes or tweets under ~600 words, pure research-findings synthesis with no drafting, or essay drafting when there is no research corpus to ground in.
create-skill
Creates a new Claude Code skill that follows the Anchored Interview pattern — ground in a CORPUS, run an interview anchored by that grounding, then produce a single ARTIFACT. Use whenever the user wants to scaffold, generate, or design an interview-style skill — phrases like "make me an anchored interview skill", "create a skill that interviews me about X and produces Y", "scaffold a skill that reads my <corpus> and writes a <artifact>", "I want a skill for spec/draft/plan/findings creation via interview", or any request to build a skill that has the ground-then-ask-then-act shape. Do NOT use for: running an anchored interview on a specific task (this skill *creates* such skills, it doesn't perform them — for that, use or create the appropriate task-specific skill); editing an existing SKILL.md; one-shot transformations with no judgment calls; or skills where there is no corpus to ground in.