skills.rest
smp4
smp4COMMUNITY
Explore all skills by this author →
GitHub

new-plan

Interview users to transform product requirements into approved SPEC.md and PLAN.md documents.

Updated Mar 2, 2026
Search Tags:#planning#documentation#specification#interview#handoff#dsl#acceptance-criteria
One-click install
npx skills add https://github.com/smp4/claude-skills --skill new-plan-smp4
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: new-plan
Source: https://github.com/smp4/claude-skills/tree/main/dot_claude/skills/new-plan
Command: npx skills add https://github.com/smp4/claude-skills --skill new-plan-smp4

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Aligns vague product ideas with disciplined planning by interviewing the user, capturing requirements, and packaging approved SPEC.md and PLAN.md documents so downstream execution teams can start with clarity.

Core Features & Use Cases

  • Interview-driven discovery: Runs a structured multi-phase interview (problem, outcomes, scope, constraints, interfaces, edge cases, acceptance criteria) before writing anything to avoid assumptions.
  • Standards-based documentation: Generates SPEC.md with traceable goals, requirements, edge cases, and DSL proposals plus PLAN.md with architecture, units, tests, risks, and handoff instructions.
  • Handoff coordination: Collects approvals, wires up GitHub issue creation or local docs, and signals /new-task when the plan is ready to execute.

Quick Start

Ask for a new plan with your feature idea so the assistant can interview you and output SPEC.md and PLAN.md for approval.

Frequently Asked Questions about new-plan

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

FAQPage Schema
How do I turn vague product ideas into structured specifications and plans?▼

Structured specifications are generated by running a multi-phase interview that captures goals, constraints, and acceptance criteria, then packaging the approved outputs into SPEC.md and PLAN.md documents for downstream execution.

What is the best way to document acceptance criteria and domain glossary links for new features?▼

Documenting acceptance criteria and domain glossary links is handled within the generated SPEC.md file, ensuring all plans trace directly to functional requirements and DSL expectations before execution begins.

How do I conduct an interview-driven discovery workflow for product requirement planning?▼

Interview-driven discovery for product planning is conducted by answering structured questions covering problem scope, outcomes, constraints, interfaces, and edge cases before any specification documentation is written.

Can I wire up GitHub issue creation and signal downstream tasks after generating a plan?▼

Yes, you can coordinate handoffs by collecting approvals, wiring up GitHub issue creation or local docs, and signaling the /new-task workflow when the SPEC.md and PLAN.md documents are ready to execute.

Does this planning approach work without assuming prior architecture review or interface definitions?▼

No, this approach requires multiphase context gathering including architecture review and interface definitions during the interview to avoid assumptions before finalizing the handoff documentation.

Related Skills

Explore More Product & Management Skills→
AcendasAcendas
2

ship-discuss

Guides feature discovery conversations from vague ideas to structured plans and specs.

Official
Advanced
blockscoutblockscout
229

implementation-plan

Generate implementation-plan.md and coding-task.md from an approved task-analysis.

Official
Intermediate
kubiyabotkubiyabot
16

azure

Manage Azure resources via the native az CLI.

Official
Advanced
MoonLadderStudiosMoonLadderStudios
12

moonspec-tasks

Convert a Moon Spec story into an executable tasks.md from spec.md and plan.md.

Official
Advanced