skills.rest
eratio08
eratio08COMMUNITY
Explore all skills by this author →
GitHub

spec-planner

Refine product requirements through structured dialogue into implementation-ready specs.

4|Updated May 21, 2020
Search Tags:#planning#architecture#templates#requirements#spec#RFC
One-click install
npx skills add https://github.com/eratio08/dotfiles --skill spec-planner-eratio08
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: spec-planner
Source: https://github.com/eratio08/dotfiles/tree/main/opencode/.config/opencode/skills/spec-planner
Command: npx skills add https://github.com/eratio08/dotfiles --skill spec-planner-eratio08

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Dialogue-driven spec development through skeptical questioning and iterative refinement to produce implementation-ready docs that align stakeholders and reduce ambiguity.

Core Features & Use Cases

  • Structured peer dialogue to clarify scope, constraints, and success criteria.
  • Generate implementation-ready artifacts using standardized templates (Feature Plan, ADR, RFC) and recommended next steps.
  • Apply to feature planning, architecture decisions, RFC/design doc creation, and work scoping across projects.

Quick Start

Initiate a planning session by stating your goal and constraints, and I will guide you through clarifying questions and drafting a plan.

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 implementation-ready spec for a new feature?▼

You can create an implementation-ready spec through dialogue-driven refinement that clarifies scope, constraints, and success criteria, ultimately producing standardized planning artifacts like Feature Plans, ADRs, or RFCs.

What is dialogue-driven spec planning and how does it work?▼

Dialogue-driven spec planning uses structured, skeptical questioning and iterative refinement to identify product requirements, align stakeholders, and reduce ambiguity before implementation begins.

Can I use this for architecture decisions and RFC creation?▼

Yes, this applies to architecture decisions and RFC creation by guiding structured dialogue to define problems, stakeholder trade-offs, and acceptance criteria across domains using standardized templates.

What is the best way to define stakeholder trade-offs during product planning?▼

Defining stakeholder trade-offs effectively requires structured peer dialogue applying skeptical questioning to clarify scope and constraints, ensuring all planning deliverables are traceable.

How do I start a scoping discussion for a new project requirement?▼

Start a scoping discussion by stating your goal and constraints to trigger guided clarifying questions, leading directly to a drafted plan with clear problem definitions and acceptance criteria.

Does this approach work for cross-domain feature planning?▼

Yes, this works for cross-domain feature planning by leveraging structured dialogue and standardized templates to satisfy constraints like problem definition, stakeholder trade-offs, and traceable deliverables.

Related Skills

Explore More Product & Management Skills→
musher-devmusher-dev

shaping-writing-problem-frames

Generate problem frame documents from a context brief.

Official
Intermediate
cill-i-amcill-i-am

writing-plans

Convert project specs into implementation plans with tasks, files, tests, and documentation.

Community
Intermediate
jamestorrevillasjamestorrevillas
3

cross-functional-collab

Translate vague business requests into technical plans with acceptance criteria.

Community
Intermediate
sustinbebustinsustinbebustin

spec-planner

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

Community
Advanced