skills.rest
shawn-sandy
shawn-sandyCOMMUNITY
Explore all skills by this author →
Website𝕏@shawnsandyGitHub

implementation-plan

Generates self-contained HTML implementation plans from Markdown specs with steps, criteria, and metadata.

Updated Jun 8, 2026
Search Tags:#planning#tdd#html generation#markdown#claude code#implementation plan#github issues
One-click install
npx skills add https://github.com/shawn-sandy/agentics-kit --skill implementation-plan-shawn-sandy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: implementation-plan
Source: https://github.com/shawn-sandy/agentics-kit/tree/main/kit/plugins/plan-agent/skills/implementation-plan
Command: npx skills add https://github.com/shawn-sandy/agentics-kit --skill implementation-plan-shawn-sandy

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Writing implementation plans by hand produces inconsistent, hard-to-track documents, and hand-editing HTML plan pages is error-prone. This Skill lets you author a small Markdown spec and renders it into a styled, interactive, self-contained HTML plan with progress tracking, acceptance criteria checkboxes, and copy-ready implementation prompts. ## Core Features & Use Cases - Markdown-to-HTML plan rendering: Author a compact spec (objective, steps with Why/Verify, acceptance criteria, tests) and render it via the bundled plan-agent-render script into a full HTML document with sidebar nav, progress bar, and status badges. - Structured planning workflow: Guided stages including codebase exploration, clarification, alignment checks, an interview that stress-tests the plan, and a mandatory Tests section classified by tier. - Advanced plan shapes: Supports RED/GREEN/VERIFY/SHIP test-driven phases and parallel ### Lane: groupings for worktree-isolated implementation, plus GitHub/GitLab issue ingestion to seed plans from tickets. - Use Case: A developer pastes a GitHub issue URL and asks for a plan; the Skill fetches the issue, explores the codebase, drafts a spec with falsifiable acceptance criteria, and delivers a rendered HTML plan whose Implement prompt hands off to a build skill. ## Quick Start Ask the agent to create an implementation plan for your objective, for example by saying: create an HTML implementation plan for adding a dark mode toggle to the settings page.

Frequently Asked Questions about implementation-plan

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate an HTML implementation plan from a Markdown file?▼

Author a Markdown spec with the required sections (Objective, Steps with Why and Verify markers, Acceptance Criteria, Verification), then run plan-agent-render <plan>.md -o <plan>.html. Exit code 1 prints exactly which required section is missing or malformed.

How do I create a plan from a GitHub issue?▼

Pass the issue URL or a bare #n as the argument. The Skill fetches the issue with gh issue view, maps the title to the objective, the body to a Context block, labels to a type hint, and records the URL in the spec frontmatter.

Can this skill implement the plan it creates?▼

No. The skill only produces plan documents and never edits source files outside the plans directory. Implementation is a separate user-initiated step handed off to the build skill via the rendered Implement prompt.

What is the RED/GREEN/VERIFY/SHIP phase structure in a plan?▼

It is a test-driven grouping of steps where failing tests are authored first, then minimal implementation, then full verification, then an optional ship phase. It applies when steps touch application source and a test runner exists, and can be forced with --tdd or suppressed with --no-tdd.

Why does my plan render fail with a frontmatter error?▼

The enumerated frontmatter keys accept only fixed values: status (todo, in-progress, completed), type (feature, fix, refactor, docs, chore), effort (low, medium, high), and workflow (auto, always, never). Any other value fails the render with a message naming the key and the valid set.

When should I use lanes instead of phases in a plan?▼

Use lanes when groups of steps touch disjoint file sets and each can be verified independently, so build can dispatch one worktree-isolated worker per lane. Use phases for long sequential work that must run in order across context windows.

Related Skills

Explore More Software Engineering Skills→
ClyptAIClyptAI

triage-issue

Explore a codebase to identify root causes and generate a GitHub issue with a TDD fix plan.

Official
Intermediate
SeanChenRSeanChenR

executing-plans

Execute written implementation plans with review checkpoints and verifications.

Community
Intermediate
nanomadernanomader
1

plan-author-review-loop

Generate and validate Markdown implementation plans with deterministic checks.

Community
Intermediate
imclabimclab
1

quick-design

Generate dated markdown Quick Design Specs for small gameplay or XR changes.

Official
Intermediate