skills.rest
rodolfochicone
rodolfochiconeCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

rc-spec

Interviews users to produce PRD, tech spec, and ADR documents.

19|1|Updated Jun 27, 2026
Search Tags:#planning#requirements#adr#technical design#interview#spec#prd
One-click install
npx skills add https://github.com/rodolfochicone/rc-project --skill rc-spec-rodolfochicone
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: rc-spec
Source: https://github.com/rodolfochicone/rc-project/tree/main/skills/promoted/rc-spec
Command: npx skills add https://github.com/rodolfochicone/rc-project --skill rc-spec-rodolfochicone

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Turning a vague feature idea into a buildable specification requires structured discovery that most teams skip, leading to specs built on unexamined assumptions. This Skill runs a guided interview that produces a product requirements document, a technical specification, and architecture decision records before any code is written. ## Core Features & Use Cases - Structured Interview Protocol: Asks one multiple-choice question at a time with a hard cap of 3 product-phase questions, enforced through an interactive question tool. - Dual-Phase Specification: Separates product intent (what and why) from technical design (how), preventing premature implementation drift, and records decisions as ADRs. - Research Grounding: Performs parallel codebase and market research before asking questions, then writes outputs to .rc/tasks/<slug>/ using PRD, tech spec, and ADR templates. - Use Case: Before building a new notification feature, run this Skill to interview stakeholders, document the chosen product approach as an ADR, and produce an approved PRD and tech spec ready for ticket breakdown. ## Quick Start Ask the agent to spec out your feature idea, for example: "Spec the webhook notifications feature before we build it."

Frequently Asked Questions about rc-spec

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

FAQPage Schema
How do I turn a feature idea into a technical specification?▼

Run a structured interview that first captures product intent (what and why), then technical design (how). The Skill writes a PRD, a tech spec, and ADRs to a task directory only after you approve each phase.

What is an ADR and when should I write one?▼

An Architecture Decision Record documents a significant decision, its alternatives, and its trade-offs. Write one whenever you choose between product approaches or make a notable technical decision during spec design.

Can I skip the interview for a simple feature?▼

No. The protocol enforces the interview for every feature regardless of perceived simplicity, because unexamined product assumptions in simple features cause the most expensive rework. The interview can be brief but must happen.

Does this Skill break the spec into implementation tickets?▼

No. Ticket breakdown is explicitly out of scope and handled by a separate step (rc-tickets). This Skill ends once the PRD, tech spec, and ADRs are approved and written to disk.

Where are the generated spec files stored?▼

Files are written to `.rc/tasks/<NN>-<slug>/` with `_prd.md`, `_techspec.md`, and an `adrs/` subdirectory. Existing task directories are reused in update mode without allocating a new counter.

Related Skills

Explore More Product & Management Skills→
Antony-FigueroaAntony-Figueroa
3

brainstorming

Turns raw ideas into structured design briefs and specifications.

Community
Intermediate
mmartinsolivmmartinsoliv

to-issues

Break plans, specs, or PRDs into dependency-ordered tracer-bullet issues.

Community
Intermediate
windmill-labswindmill-labs
17.8k

codebase-design

Designs deep modules with small interfaces, clean seams, and testable adapters.

Official
Intermediate
MS33834MS33834

Doc Co-Authoring Workflow

Guide teams through staged co-authoring of RFCs, design docs, and PRDs.

Community
Advanced