skills.rest
danabrams
danabramsCOMMUNITY
Explore all skills by this author →
GitHub

gromit-refine

Refine vague backlog ideas into structured specifications with acceptance criteria.

3|Updated Feb 5, 2026
Search Tags:#planning#collaboration#codebase#specification#backlog#acceptance-criteria#refine
One-click install
npx skills add https://github.com/danabrams/gromit --skill gromit-refine
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gromit-refine
Source: https://github.com/danabrams/gromit/tree/main/skills/gromit-refine
Command: npx skills add https://github.com/danabrams/gromit --skill gromit-refine

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Guides codebase-aware conversation to transform vague backlog ideas into clear specifications, with acceptance criteria, decisions, and context.

Core Features & Use Cases

  • Facilitates a structured refinement workflow: reads the codebase, asks clarifying questions one at a time, and helps produce a formal spec.
  • Generates a .gromit/specs/<name>.md spec including acceptance criteria, decisions, and context.
  • Integrates with the Gromit four-stage pipeline (Capture, Refine, Plan, Decompose) to convert ideas into implementable plans.

Quick Start

Start by describing a backlog item or idea; I will guide you through clarifying questions and generate a complete spec.

Frequently Asked Questions about gromit-refine

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

FAQPage Schema
How do I turn vague backlog ideas into structured specifications?▼

To refine vague backlog ideas into structured specifications, you describe the item and the tool guides a codebase-aware conversation. It asks clarifying questions one at a time to produce a formal spec with acceptance criteria, decisions, and context.

What is the best way to create formal specs with acceptance criteria from a codebase?▼

Creating formal specs with acceptance criteria from a codebase involves exploring the repository to ask targeted refinement questions. This process generates a standardized .gromit/specs specification document including project decisions and context.

How does codebase-aware refinement work for software planning?▼

Codebase-aware refinement works by reading the repository context to guide one-question-at-a-time clarification. This ensures the resulting specification accurately reflects the existing codebase structure and project decisions.

Can I use this to generate a .gromit/specs markdown document for my project?▼

Yes, you can use this to generate a .gromit/specs markdown document for your project. The refinement workflow outputs a formal specification file named .gromit/specs/<name>.md containing acceptance criteria and context.

Does this specification tool integrate with a broader planning pipeline?▼

Yes, the specification tool integrates with the broader Gromit planning pipeline. It connects the Capture, Refine, Plan, and Decompose stages to convert ideas into implementable plans.

What format does the generated specification enforce for backlog refinement?▼

The generated specification enforces a consistent format compatible with the Gromit planning pipeline. It includes structured sections for acceptance criteria, decisions, and context within a markdown document.

Related Skills

Explore More Software Engineering Skills→
heimeshoffheimeshoff
27

quick-capture

Route raw ideas to bounded contexts and create backlog tasks.

Community
Intermediate
shopsysshopsys
349

create-plan

Generate iterative implementation plans from codebase patterns and Jira tickets.

Official
Advanced
NNPopovNNPopov
2

grill-with-docs

Clarify product plans against codebase, glossary, and architecture notes.

Community
Advanced
Agent-Pattern-LabsAgent-Pattern-Labs
4

notion

Manage Notion pages, databases, and blocks through the API.

Official
Intermediate