create-a-plan

Convert rough specs into a structured PLAN.md with verification steps.

11|6|Updated Apr 11, 2024
One-click install
npx skills add https://github.com/cartridge-gg/nums --skill create-a-plan
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: create-a-plan
Source: https://github.com/cartridge-gg/nums/tree/main/.agents/skills/create-a-plan
Command: npx skills add https://github.com/cartridge-gg/nums --skill create-a-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill runs a structured technical interview to turn a rough idea or existing spec into a detailed, implementable plan that can be executed in parallel across workstreams.

Core Features & Use Cases

  • Structured Interview: Systematically elicit goals, constraints, risks, and gaps to form a concrete PLAN.md.
  • Plan for Parallelization: Organize work into foundations, independent streams, and integration steps.
  • Outcome: Produce PLAN.md in the repository root that can be reviewed, updated, and tracked.

Quick Start

Use the create-a-plan skill to convert a rough spec into a step-by-step PLAN.md ready for distribution to engineers.

Frequently Asked Questions about create-a-plan

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

FAQPage Schema
How do I turn a rough software spec into an actionable plan?▼

To turn a rough software spec into an actionable plan, use a structured interview process to elicit goals, constraints, and risks, producing a concrete PLAN.md document for your repository.

What is the best way to structure a plan for parallel engineering workstreams?▼

Structuring a plan for parallel engineering workstreams involves organizing tasks into foundations, independent development streams, and integration steps, resulting in a tracked PLAN.md file.

Can I automate risk analysis and dependency mapping for software architecture?▼

Yes, you can automate risk analysis and dependency mapping by running a structured technical interview that identifies gaps and constraints, generating an implementable architecture plan.

Does generating a PLAN.md require a complete product specification beforehand?▼

Generating a PLAN.md does not require a complete specification; the skill is designed to convert rough ideas and incomplete specs into a structured, implementable plan through discovery rounds.

How to conduct a technical interview to gather software project requirements?▼

Conducting a technical interview for software requirements involves systematically questioning stakeholders to extract goals, constraints, and risks, which forms the basis of the final PLAN.md.

When do I need to write a PLAN.md file at my repository root?▼

You need to write a PLAN.md file at your repository root when your software engineering project requires structured planning, explicit verification steps, and parallel task distribution across engineers.