Plugins

7 plugins

PRD to Implementation Plan

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

11 skills · plugin

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

7 skills · plugin

Component Spec and Pattern Library

Document component anatomy, variants, and usage patterns for consistent implementation.

5 skills · plugin

Growth Loop Implementation

Identify the right growth loop mechanism, then build the acquisition and expansion motions to drive it.

3 skills · plugin

Implement Plan with Git Workflow

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

6 skills · plugin

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 · plugin

Reporting and summary skills for the Han suite. Turns feature specifications into plain-language stakeholder summaries (also called executive or business summaries) with diagrams, for sharing with non-technical stakeholders before implementation kicks off.

2 skills · plugin

Results for “implementation”

26 skills

notion-spec-to-implementation

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

23.3k · bundle

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.

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.

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

180-name-aa5fe744

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

More results

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.

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

Conducts structured requirements workshops to produce feature specifications, user stories, EARS-format functional requirements, acceptance criteria, and implementation checklists.

10.4k · bundle

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.

Implements work from a PRD or set of issues using TDD, typechecking, and regular testing, then reviews and commits the changes.

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.

create-technical-spike

Create time-boxed technical spike documents for researching and resolving critical development decisions before implementation.

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

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

openspec-explore

Enter explore mode to think through ideas, investigate problems, and clarify requirements before implementation, with optional OpenSpec artifact creation.

Chains /mvp and /backend-spec to analyze an app from video, screenshots, or description, then generate implementation stories from the analysis.

Generate a structured specification document before writing implementation code, validating scope, drafting specs, and registering them in the project.

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.

Analyzes dependencies between stories, code modules, tickets, or specs to compute an optimal implementation order with parallel batches, cycle detection, and critical path analysis.

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.