skills.rest
roerohan
roerohanCOMMUNITY
Explore all skills by this author →
Website𝕏@roerohanGitHub

spec-planner

Clarify product requirements and generate testable specifications with effort estimates.

27|1|Updated May 13, 2026
Search Tags:#spec writing#feature planning#architecture decisions#tradeoff analysis#requirement clarification#RFC creation#work scoping
One-click install
npx skills add https://github.com/roerohan/skills --skill spec-planner-roerohan
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: spec-planner
Source: https://github.com/roerohan/skills/tree/main/spec-planner
Command: npx skills add https://github.com/roerohan/skills --skill spec-planner-roerohan

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Vague, incomplete specifications lead to engineering rework, misaligned stakeholder expectations, and wasted development effort. This Skill eliminates that risk by enforcing rigorous requirement clarification and structured, dialogue-driven planning before any implementation work begins.

Core Features & Use Cases

  • Skeptical Requirement Clarification: Asks 3-5 targeted, pointed questions to resolve scope, motivation, constraint, and edge case gaps upfront, even for seemingly complete feature requests.
  • Structured 5-Phase Workflow: Moves systematically from initial clarification through system discovery, spec drafting, refinement, and final delivery, with explicit phase transitions and state tracking at every step.
  • Built-In Planning Frameworks: Includes pre-built templates for feature plans, architecture decision records (ADRs), and RFCs, plus tools for tradeoff analysis, effort estimation, and technical debt ROI calculation.
  • Use Case Example: When you have a feature idea like "add user authentication", use this Skill to walk through scope constraints, evaluate tradeoffs between different auth providers, and produce a detailed spec with ordered deliverables, acceptance criteria, and risk mitigations.

Quick Start

Invoke the spec-planner skill to create a detailed implementation specification for your planned new feature, including clarified requirements, tradeoff analysis, and effort estimates.

Frequently Asked Questions about spec-planner

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

FAQPage Schema
How do I write a feature spec from a vague product idea?▼

Spec writing for software engineering requires skeptical requirement clarification to resolve scope and edge case gaps upfront. This ensures detailed implementation specifications with acceptance criteria, preventing engineering rework and misaligned stakeholder expectations.

How do I create an architecture decision record with tradeoff analysis?▼

Create architecture decision records by applying built-in planning frameworks that formalize tradeoff analysis and effort estimation. This evaluates technical constraints to produce standardized documentation for architecture decisions and technical debt ROI calculations.

What is the best way to scope software engineering work for new features?▼

The best way to scope work is through a structured 5-phase workflow moving from requirement clarification to system discovery and spec delivery. This systematic process tracks state transitions to produce effort-estimated specifications with ordered deliverables.

Can I use this to create an RFC for my engineering team?▼

Yes, you can create RFCs using standardized output templates designed for RFC creation. The process clarifies technical motivations and constraints upfront, resulting in a structured proposal ready for stakeholder review.

Why does feature planning fail without requirement clarification?▼

Feature planning fails without requirement clarification because incomplete specifications cause engineering rework and misaligned expectations. Applying targeted dialogue to resolve ambiguous scope ensures detailed implementation specs that prevent wasted development effort.

Related Skills

Explore More Product & Management Skills→
WcofWcof
1

pm-need

Transform vague product ideas into a structured PMContext through automated collection and refinement.

Community
Advanced
cchrisvcchrisv

to-issues

Break development plans into dependency-aware implementation issues with acceptance criteria.

Community
Intermediate
ApothecaryManApothecaryMan

problem-analyzer

Analyze technical problems through database inspection and visual diagramming.

Community
Advanced
achmfachmf

plan-writing

Create structured, verifiable task plans for software development projects.

Community
Intermediate