spec-planner

Guide structured refinement dialogues to produce documented software specifications.

Updated Jun 12, 2025

Search Tags:#planning #architecture #ADR #spec #RFC #design-doc

Ready to run

npx skills add https://github.com/stevoland/dotfiles --skill spec-planner

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: spec-planner
Source: https://github.com/stevoland/dotfiles/tree/main/opencode/skill/spec-planner
Command: npx skills add https://github.com/stevoland/dotfiles --skill spec-planner

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ambiguity in requirements and architecture decisions slows software delivery. This Skill guides a structured, skeptical dialogue to surface gaps, align stakeholders, and produce clear, implementable specifications.

Core Features & Use Cases

Dialogue-driven questioning to surface scope, motivation, constraints, edge cases, and success criteria.
Structured workflow following the phases CLARIFY → DISCOVER → DRAFT → REFINE → DONE with explicit state transitions.
Template-guided outputs for RFCs, ADRs, feature plans, and architecture decisions using established templates.
Use Case: When launching a new feature or refactor, run this Skill to yield an implementation-ready spec you can hand to engineering.

Quick Start

Trigger the spec-planner with a feature idea (e.g., "spec this out") to begin the dialogue and generate an actionable spec.

Frequently Asked Questions about spec-planner

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

FAQPage Schema

How do I write an RFC or design doc for a new software feature?▼

To write an RFC or design doc, you need a structured refinement process that clarifies scope and constraints. This Skill guides a dialogue-driven workflow to surface gaps and produce template-guided, implementation-ready specifications.

What is the best way to scope ambiguous software requirements before implementation?▼

Scoping ambiguous requirements involves skeptical questioning to align stakeholders. This Skill enforces a structured phase workflow—Clarify, Discover, Draft, Refine—to surface edge cases and yield documented, actionable specs.

How do I create an Architecture Decision Record (ADR) from a rough idea?▼

Creating an ADR from a rough idea requires discovering architectural constraints and motivations. This Skill applies a dialogue-driven approach to refine your idea and outputs a documented decision record using established templates.

Can I use a dialogue-driven process to plan a technical refactor?▼

Yes, planning a technical refactor benefits from dialogue-driven spec planning. This Skill guides you through structured phases to define success criteria and generates an actionable spec to hand to engineering.

When do I need a structured workflow for feature planning?▼

You need a structured workflow for feature planning when requirements lack clarity or stakeholder alignment. This Skill solves ambiguity by enforcing explicit state transitions across clarification, discovery, and drafting phases.

Does spec planning work for generating work scoping across software projects?▼

Spec planning works for work scoping by driving a skeptical dialogue to surface project constraints. This Skill produces documented specs that define boundaries and implementation readiness for engineering teams.