plugin-dev-planner

Generates phased plugin development plans with tasks, gates, and evidence mappings.

Updated Jul 3, 2026
One-click install
npx skills add https://github.com/LYGOLANG/fufan-cc-flow --skill plugin-dev-planner-lygolang
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plugin-dev-planner
Source: https://github.com/LYGOLANG/fufan-cc-flow/tree/main/bundled-plugins/plugin-builder/skills/plugin-dev-planner
Command: npx skills add https://github.com/LYGOLANG/fufan-cc-flow --skill plugin-dev-planner-lygolang

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Turning an approved plugin specification and design into an executable development plan is error-prone: teams often split work by frontend/backend layers, lose traceability between requirements and tasks, and discover host-integration risks too late. This Skill converts a gated Plugin-Spec.md, plugin.yaml, and Plugin-Design.md into a PLUGIN-DEV-PLAN.md organized around runnable vertical slices. ## Core Features & Use Cases - Vertical-slice planning: Structures work into fixed phases (Scaffold, Local Round-trip, State, UI to Agent, Agent to UI, Feature Slices, Security, Packaging, Smoke) so each phase produces a runnable, observable capability. - Full traceability: Maps every must requirement and acceptance criterion to implementation tasks, verification tasks, targets, and evidence, with a Host Verification Matrix and Security Verification Matrix. - Task rigor and rollback: Every task carries a stable ID, files, dependencies, commands, completion criteria, evidence, failure rollback, and parallel-safety notes. - Use Case: After your interactive plugin design passes review, run this Skill to produce a phase-gated plan where the first critical path proves the minimal plugin round-trip before any complex business UI is built. ## Quick Start Ask the agent to generate the PLUGIN-DEV-PLAN.md from the approved Plugin-Spec.md, plugin.yaml, and Plugin-Design.md in the current plugin project.

Frequently Asked Questions about plugin-dev-planner

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

FAQPage Schema
How do I create a development plan for a Claude Code plugin?▼

Provide an approved Plugin-Spec.md, a schema-valid plugin.yaml, and a Plugin-Design.md, then run this Skill. It produces a PLUGIN-DEV-PLAN.md with phased tasks, commands, completion criteria, and evidence mappings.

What inputs are required before generating a plugin dev plan?▼

The Skill requires Plugin-Spec.md at SPEC_READY, plugin.yaml passing schema validation, Plugin-Design.md at DESIGN_READY, Plugin-Project-State.md at DESIGN_READY, and prototype evidence for Class C projects.

How are requirements traced to tasks in the plan?▼

Every must requirement and required acceptance criterion maps to an implementation task, a verification task, a target, and an evidence type. Traceability, host verification, and security matrices keep the mappings auditable.

Does the plan include real host installation testing?▼

No. Real host install and end-to-end tests are registered in the Host Verification Matrix and executed centrally in the fifth step by the checker. Development-phase tasks only cover local builds, probes, and package smoke tests.

When should planning return to an upstream skill instead?▼

If the spec has P0 open questions, a required target lacks an implementation path, acceptance criteria are untestable, or prototype failures are unresolved, the Skill returns to the corresponding upstream skill rather than hiding problems in the plan.