spec-planner

Guides iterative clarification and drafting of implementation-ready specifications for software features and architectural decisions.

Updated Feb 19, 2026
One-click install
npx skills add https://github.com/sustinbebustin/.dotfiles --skill spec-planner-sustinbebustin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec-planner
Source: https://github.com/sustinbebustin/.dotfiles/tree/main/home/.claude/skills/spec-planner
Command: npx skills add https://github.com/sustinbebustin/.dotfiles --skill spec-planner-sustinbebustin

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the creation of implementation-ready specifications by guiding users through a structured dialogue, ensuring all aspects of a feature or decision are thoroughly considered.

Core Features & Use Cases

  • Iterative Refinement: Engages in a question-and-answer process to clarify scope, constraints, and requirements.
  • Structured Planning: Utilizes defined phases (Clarify, Discover, Draft, Refine) to build comprehensive specs.
  • Use Case: When a product manager needs to define a new feature, they can invoke the spec-planner to systematically work through the requirements, potential challenges, and deliverables, resulting in a clear, actionable plan.

Quick Start

Use the spec-planner to help define the scope for a new user authentication module.

Frequently Asked Questions about spec-planner

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

FAQPage Schema
How do I write implementation-ready software feature specifications through dialogue?

Implementation-ready feature specifications are developed by guiding users through iterative dialogue, structured questioning, and trade-off analysis across clarification, discovery, drafting, and refinement phases to ensure comprehensive requirements coverage.

What is the best way to gather requirements for a new software architecture decision?

Requirements gathering for architectural decisions is best achieved through a structured Q&A process that applies skeptical questioning to clarify scope, identify constraints, and analyze trade-offs, resulting in a clear and actionable architectural plan.

How do I systematically define the scope for a new user authentication module?

To define scope for an authentication module, engage in iterative refinement that systematically works through requirements, potential challenges, and deliverables using defined planning phases to produce a comprehensive specification.

Can I use dialogue-driven planning to refine vague feature development ideas?

Dialogue-driven planning refines vague feature ideas by walking through discovery and drafting phases, leveraging structured questioning to expose hidden constraints and clarify exact requirements before producing the final spec.

What are the limitations of using a dialogue-based approach for specification development?

Dialogue-based specification development relies heavily on the user providing accurate answers during the iterative refinement process, meaning incomplete domain knowledge or vague responses can limit the depth of the resulting architectural trade-off analysis.

Does the spec-planner skill support structured phases for software requirements gathering?

Spec-planner supports requirements gathering through four structured phases: Clarify, Discover, Draft, and Refine, each designed to systematically build comprehensive and implementation-ready software specifications.