plugin-spec-builder

Interviews users to generate Plugin-Spec.md, plugin.yaml, and changelogs for interactive plugins.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Turning a vague plugin idea into a buildable specification is hard: users describe features loosely, forget permissions, hosts, and failure handling, and developers end up building the wrong thing. This Skill runs a structured interview that converts scattered ideas into a complete, validated plugin specification. ## Core Features & Use Cases - Interview-driven spec generation: Asks targeted follow-up questions across five phases (basics, golden path, agent collaboration, data/permissions, scope and acceptance) instead of dumping a long questionnaire. - Dual modes: Runs a 0-to-1 workflow when no Plugin-Spec.md exists, or an iteration workflow that classifies changes, detects conflicts, and updates requirement IDs and changelogs. - Validated artifacts: Produces Plugin-Spec.md, Plugin-Spec-CHANGELOG.md, plugin.yaml, and Plugin-Project-State.md, then runs a central validator script before marking the spec ready. - Use Case: A user says "I want a plugin that edits video timelines in Claude Code." The Skill interviews them about direct manipulation, agent handoff, file scope, and acceptance criteria, then outputs a spec with numbered REQ/UX/HOST/DATA/SEC/AC requirements ready for the design phase. ## Quick Start Ask the assistant to help you turn your new interactive plugin idea into a complete Plugin-Spec.md and plugin.yaml through a guided interview.

Frequently Asked Questions about plugin-spec-builder

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

FAQPage Schema
How do I turn a plugin idea into a formal specification?▼

Describe your plugin idea in plain language and the Skill interviews you across five phases covering users, golden path, agent collaboration, permissions, and acceptance criteria. It then generates Plugin-Spec.md, plugin.yaml, and a changelog once all required information is gathered.

What files does the plugin spec workflow generate?▼

It generates Plugin-Spec.md with numbered REQ/UX/HOST/DATA/SEC/NFR/AC requirements, plugin.yaml as the machine-readable manifest, Plugin-Spec-CHANGELOG.md for change history, and Plugin-Project-State.md tracking phase and quality gate status.

How do I update an existing plugin specification when requirements change?▼

When Plugin-Spec.md already exists, the Skill switches to iteration mode. It classifies your change, detects conflicts with existing requirements and host capabilities, updates affected requirement IDs, and records the impact and phase rollback in the changelog.

Which hosts can a plugin spec target?▼

Specs can target Claude Code, Claude Desktop, claude.ai, ChatGPT, and Codex, each marked as required, optional, or experimental. The Skill checks that the chosen development form (companion-web-app, mcp-app, or hybrid) matches each host's actual UI capabilities.

When should I not use an interactive plugin spec?▼

If your idea has no GUI-specific value such as direct manipulation, persistent state, or visual comparison, the Skill will tell you a plain conversational Skill or MCP tool is a better fit instead of forcing an interactive plugin.