Packs

4 packs

PRD to Implementation Plan

Transform a raw product idea into a structured PRD and then into a technical implementation plan with issues.

11 skills · pack

Common base skills including documentation generators, implementation planning, and utility tools

7 skills · pack

Planning skills for the Han suite: specifying, planning, sequencing, breaking down, and stress-testing work before implementation. Home of plan-a-feature, plan-implementation, plan-a-phased-build, plan-work-items, and iterative-plan-review, plus the discussion-facilitator agent. Depends on han-communication and han-core; bundled by the han meta-plugin.

5 skills · pack

Implement Plan with Git Workflow

Execute a predefined implementation plan step by step using isolated git worktrees and structured version control.

6 skills · pack

Results for “implementation-plan”

19 skills

create-implementation-plan

Generate structured, machine-readable implementation plans for features, refactoring, upgrades, or infrastructure changes.

update-implementation-plan

Update an existing implementation plan file with new or updated requirements for features, refactoring, package upgrades, design, architecture, or infrastructure.

notion-spec-to-implementation

Convert Notion product specs into linked implementation plans, tasks, and progress tracking with structured workflows.

23.3k · bundle

Turns a mature product plan into a rough implementation plan with high-level steps, maturity and verification marks, and a risks section.

Breaks a PRD into a multi-phase implementation plan using tracer-bullet vertical slices, saved as a local Markdown file in ./plans/.

Verifies each step of a rough implementation plan against source code and current documentation, attaching proof and marking steps as verified or unverified.

More results

breakdown-feature-implementation

Creates detailed technical implementation plans for features based on a Feature PRD, including system architecture, database schema, API design, and frontend component hierarchy.

Transforms a rough idea into a detailed design document with an implementation plan through iterative requirements clarification, research, design, and planning.

180-name-aa5fe744

Guides the agent through structured protocols for writing technical specifications, implementation plans, and summaries, with file naming and task directory conventions.

Analyzes an app from video, screenshots, or description, then generates implementation stories in dependency order.

Interviews the user in depth about a plan, probing technical implementation, UI/UX, risks, tradeoffs, and missing decisions before writing or refining a spec.

product-capability

Translate product intent, PRDs, or roadmap discussions into explicit, implementation-ready capability plans with constraints, invariants, interfaces, and open questions before multi-service work begins.

Guides collaborative dialogue to turn ideas into approved designs and specs before any implementation begins.

Guides collaborative dialogue to turn ideas into approved designs and specs before any implementation begins.

Guides collaborative dialogue to turn ideas into approved designs and specs before any implementation begins.

Guides collaborative dialogue to turn ideas into fully formed designs and specs before any implementation begins.

Guides collaborative dialogue to turn ideas into designs and specs, exploring intent and requirements before any implementation.

Guides collaborative dialogue to turn ideas into fully formed designs and specs, exploring intent, requirements, and design before implementation.

agentskillexchange

five-element-spec-scope-before-coding

Translate a vague request or GitHub issue into a concrete, testable spec using five structured elements (problem, scope, acceptance criteria, edge cases, success criterion) before writing any code. Prevents scope creep, PR churn, and mid-implementation pivots.