spec-writer

Name: spec-writer
Availability: InStock
Author: andregusman-raiz

Generate standardized technical SPEC documents for features, issues, and refactors.

19|4|Updated Mar 7, 2026

Search Tags:#workflow #template #documentation #spec #feature #issue #acceptance-criteria

Ready to run

npx skills add https://github.com/andregusman-raiz/a-gusman-claude --skill spec-writer-andregusman-raiz

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: spec-writer
Source: https://github.com/andregusman-raiz/a-gusman-claude/tree/main/skills/spec-writer
Command: npx skills add https://github.com/andregusman-raiz/a-gusman-claude --skill spec-writer-andregusman-raiz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Dificulta padronizar SPECs para features, issues e refactors, levando a inconsistências e retrabalho na fase de planejamento e documentação.

Core Features & Use Cases

Template completo de SPEC com Objetivo, Contexto, Escopo, Requisitos Funcionais, Requisitos Não-Funcionais, Edge Cases e Critérios de Aceite.
Template minimal para bugs (SPEC simples) com campos essenciais.
Orientação para mapear issues do GitHub para SPECs com convenções de nomenclatura e fluxo de trabalho.

Quick Start

Create a complete SPEC document for a new feature or issue.

Frequently Asked Questions about spec-writer

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

FAQPage Schema

How do I standardize technical SPEC documents for features and issues consistently?▼

To standardize SPEC documents for features and issues, apply a structured template covering objective, context, scope, functional requirements, edge cases, and acceptance criteria. This enforces consistency and reduces rework during the planning phase across product and engineering workflows.

What should be included in a feature SPEC template to unify planning artifacts?▼

A feature SPEC template should include the objective, context, scope, functional requirements, non-functional requirements, edge cases, and acceptance criteria. This structure unifies planning artifacts and ensures comprehensive technical documentation for engineering teams.

Can I use a minimal SPEC template for bugs instead of a full feature document?▼

Yes, you can use a minimal SPEC template for bugs. This simpler documentation format includes only essential fields, streamlining the issue tracking process without the overhead of a complete feature specification covering full scope and non-functional requirements.

What is the best way to map GitHub issues to SPEC documents with naming conventions?▼

Mapping GitHub issues to SPEC documents requires establishing clear naming conventions and workflow guidelines. This ensures each issue links directly to its corresponding technical specification, maintaining traceability between development tasks and planning artifacts.

When do I need to write SPEC documents for refactoring tasks versus new features?▼

SPEC documents for refactoring tasks are needed alongside new feature specifications to unify all planning artifacts. Generating standardized technical documentation for refactors ensures scope, requirements, and acceptance criteria are defined before engineering work begins.

Does this SPEC documentation approach work for both product and engineering workflows?▼

Yes, this SPEC documentation approach works for both product and engineering workflows. It standardizes technical documents for features, issues, and refactors, ensuring consistent planning artifacts that bridge product requirements with engineering acceptance criteria.