skills.rest
edumesones
edumesonesCOMMUNITY
Explore all skills by this author →
GitHub

spec-architect

Guide structured interviews to elicit complete specifications before coding.

Updated Feb 5, 2026
Search Tags:#specification#requirements#clarification#interview#product-management#user-stories#acceptance-criteria
One-click install
npx skills add https://github.com/edumesones/azure--demo --skill spec-architect-edumesones
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: spec-architect
Source: https://github.com/edumesones/azure--demo/tree/main/.claude/skills/spec-architect
Command: npx skills add https://github.com/edumesones/azure--demo --skill spec-architect-edumesones

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill guides teams to transform vague concepts into well-defined, testable specifications before any implementation, reducing ambiguity and downstream rework.

Core Features & Use Cases

  • Structured interviews: A formal protocol that surfaces requirements, risks, and acceptance criteria.
  • Phase-driven exploration: Covers user stories, technical constraints, edge cases, and success metrics.
  • Documentation handoff: Produces a professional spec document suitable for teams to implement from.

Quick Start

Start the interview workflow with /interview FEAT-XXX to begin Phase 1 (INTERVIEW).

Frequently Asked Questions about spec-architect

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

FAQPage Schema
How do I turn rough product ideas into technical specifications before coding?▼

Technical specifications are generated through a structured interview workflow that elicits user stories, technical constraints, edge cases, and acceptance criteria, producing a ready-to-implement design artifact.

What is the best way to write user stories and acceptance criteria from vague concepts?▼

Writing user stories and acceptance criteria from vague concepts is achieved via a phase-driven exploration protocol that surfaces requirements, risks, and success metrics, reducing ambiguity and downstream rework.

How do I conduct a requirements interview to gather complete product specifications?▼

A requirements interview is conducted using a formal guided protocol that records decisions throughout the session, advancing phase by phase until a professional spec document is delivered for team handoff.

Does this requirements clarification process work for feature development from scratch?▼

Yes, requirements clarification applies directly to feature development from scratch, guiding teams to transform vague concepts into well-defined, testable specifications before any implementation begins.

When do I need a structured specification process instead of writing code directly?▼

A structured specification process is needed when rough ideas lack clarity, requiring elicitation of technical constraints and edge cases to produce a validated requirements document suitable for implementation.

Related Skills

Explore More Product & Management Skills→
JustinWangJPJustinWangJP
6

brainstorming

Guide teams through structured brainstorming to produce design documents and implementation plans.

Community
Advanced
cchrisvcchrisv

to-issues

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

Community
Intermediate
omeragaakbasomeragaakbas

user-stories

Generate testable user stories with acceptance criteria for product features.

Community
Intermediate
pelcherspelchers

gathering-requirements

Extract functional and non-functional requirements from product specifications and stakeholder input.

Community
Advanced