skills.rest
afonsoft
afonsoftCOMMUNITY
Explore all skills by this author →
Website𝕏@afonsoftGitHub

write-specs

Interviews users in Portuguese and writes Spec-Driven Development documents before implementation.

Updated Jul 21, 2026
Search Tags:#planning#documentation#requirements#interview#spec#sdd#spec-driven development
One-click install
npx skills add https://github.com/afonsoft/gamehub --skill write-specs-afonsoft
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: write-specs
Source: https://github.com/afonsoft/gamehub/tree/main/.claude/skills/write-specs
Command: npx skills add https://github.com/afonsoft/gamehub --skill write-specs-afonsoft

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Teams often start coding from vague or underspecified requests, leading to rework and misaligned expectations. This Skill structures the requirements phase by interviewing the user in Portuguese (pt-BR), mapping decisions as a design tree, and producing a complete SPEC SDD document that becomes the single source of truth before any implementation begins. ## Core Features & Use Cases - Structured Interview Rounds: Maps the request as a design tree and asks the frontier of open decisions in rounds, always in Portuguese with recommended answers to accelerate convergence. - SPEC SDD Generation: Writes a complete .specs/SPEC-{YYYYMMDD}-{feature}.md file covering metadata, user story, scope, requirements, API contracts, BDD acceptance criteria, task plan, guardrails, and Definition of Done. - Approval Gate: Blocks implementation until the user explicitly approves the SPEC and its status is set to Approved. - Use Case: A developer receives a vague request like "add notifications". The Skill interviews the user about identity, scope, stack, data, API, and validation, then produces an approved SPEC that an implementation skill can execute without ambiguity. ## Quick Start Ask the assistant to use the write-specs skill to create a SPEC for your new feature before any implementation begins.

Frequently Asked Questions about write-specs

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

FAQPage Schema
How do I write a feature specification before implementation?▼

Use this Skill to interview stakeholders in structured question rounds, then generate a SPEC SDD file in .specs/ covering user story, scope, requirements, acceptance criteria, and a task plan. Implementation only starts after the user approves the SPEC.

What is a SPEC SDD document?▼

A SPEC SDD is a Spec-Driven Development document that serves as the single source of truth before coding. It contains metadata, user story, scope, technical context, numbered requirements, API contracts, BDD acceptance criteria, task plan, guardrails, and a Definition of Done.

Does the write-specs skill write implementation code?▼

No, the Skill explicitly forbids writing implementation code. Its only output is the approved SPEC document; execution is delegated to separate implementation skills such as execute-spec.

What language does the skill use when asking questions?▼

All questions directed at the user are written in Portuguese (pt-BR), including recommended answers for each question. The Skill's internal instructions and reasoning remain in English.

What happens when requirements cannot be answered?▼

Unanswered items are marked as [A DEFINIR] in the SPEC rather than guessed. The Skill targets no more than three such placeholders; if more exist, the interview rounds continue until the design tree frontier is empty.

Related Skills

Explore More Software Engineering Skills→
DynamoDSDynamoDS
2.0k

dynamo-jira-ticket

Generate structured Jira tickets for the Dynamo project from bug reports and failing tests.

Official
Intermediate
Jia-Hong-PengJia-Hong-Peng

ship

Automate Git code shipping from branch merge to pull request creation.

Community
Advanced
EmasoftEmasoft

eia-github-project-workflow

Create GitHub Project boards and issues with acceptance criteria for multi-developer workflows.

Community
Advanced
Pear-CommercePear-Commerce

gsd-quick

Execute small development tasks with atomic commits and STATE.md tracking.

Official
Intermediate