gromit-plan

Plan software implementation from a spec into architecture, test strategy, and task plan.

3|Updated Feb 5, 2026
One-click install
npx skills add https://github.com/danabrams/gromit --skill gromit-plan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gromit-plan
Source: https://github.com/danabrams/gromit/tree/main/skills/gromit-plan
Command: npx skills add https://github.com/danabrams/gromit --skill gromit-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Planning a software implementation from a written spec often lacks structured guidance, leading to misalignment between stakeholders and engineers. This skill provides a checkpointed workflow to translate a spec into an architecture proposal, a test strategy, and a concrete task plan that can be reviewed and refined.

Core Features & Use Cases

  • Proposes architecture and testing strategy based on the spec.
  • Reads the spec from .gromit/specs/<name>.md and analyzes the codebase to inform decisions.
  • Produces a human-reviewable implementation plan that can be decomposed into actionable tasks.

Quick Start

Provide a spec name to start the planning session and generate an implementation plan.

Frequently Asked Questions about gromit-plan

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

FAQPage Schema
How do I turn a software specification into an actionable implementation plan?

To turn a software specification into an implementation plan, provide the spec name so the skill can read it, analyze your codebase, and propose an architecture, test strategy, and decomposable task plan with review checkpoints.

What is the best way to propose software architecture from a written spec?

The best way to propose software architecture from a written spec is using a checkpointed workflow that reads the specification file and analyzes the existing codebase to inform early architecture decisions and task decomposition.

How do I decompose project specifications into actionable development tasks?

You can decompose project specifications into actionable development tasks by processing the spec through a structured workflow that outputs a human-reviewable implementation plan designed for further task breakdown.

Do I need a specific file format to generate a test strategy and architecture proposal?

Yes, you need a specific file format to generate a test strategy and architecture proposal; the skill reads specifications directly from the .gromit/specs/<name>.md markdown file path.

When do I need a checkpointed workflow for task decomposition?

You need a checkpointed workflow for task decomposition when planning software projects where early architecture decisions require structured review and alignment between stakeholders and engineers before implementation begins.