spec-writer

Transform feature ideas into structured implementation specifications with acceptance criteria.

11|2|Updated Jan 19, 2026
One-click install
npx skills add https://github.com/Viniciuscarvalho/Feature-marker --skill spec-writer-viniciuscarvalho
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec-writer
Source: https://github.com/Viniciuscarvalho/Feature-marker/tree/main/feature-marker-dist/feature-marker/resources/spec-workflow/skills/spec-writer
Command: npx skills add https://github.com/Viniciuscarvalho/Feature-marker --skill spec-writer-viniciuscarvalho

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Transform ideas into clear, executable specifications that capture requirements, architecture decisions, and acceptance criteria, preventing scope creep and misalignment between product and engineering teams.

Core Features & Use Cases

  • Interactive dialogue to extract requirements, constraints, and success metrics.
  • Supports multiple modes (interactive, autonomous, revision) to fit diverse workflows.
  • Produces a structured spec with sections like Architecture, Data Model, API design, and Testing Strategy, plus a Revision History.
  • Integrates with project governance (templates, project DNA references) to enforce consistency.

Quick Start

Provide a complete, engineer-ready specification for a given feature idea, including requirements, design decisions, and acceptance criteria.

Frequently Asked Questions about spec-writer

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

FAQPage Schema
How do I turn feature ideas into detailed implementation specifications?

To turn feature ideas into detailed implementation specifications, use interactive dialogue to extract requirements, constraints, and success metrics, producing a structured output with architecture, data model, and API design sections.

What is the best way to prevent scope creep when writing design documents?

Preventing scope creep when writing design documents requires capturing clear requirements, architecture decisions, and acceptance criteria in a structured specification, ensuring alignment between product and engineering teams.

How do I generate acceptance criteria and testing strategies for a new project?

To generate acceptance criteria and testing strategies for a new project, apply a structured specification template that captures design decisions and success metrics throughout the feature development lifecycle.

Can I use autonomous workflows to produce engineer-ready project specifications?

Yes, you can use autonomous workflows to produce engineer-ready project specifications, supported by multiple modes that fit diverse workflows alongside interactive dialogue and revision tracking.

Do I need project DNA references to maintain consistency in spec writing?

Yes, integrating project DNA references and templates into spec writing enforces consistency and project governance, ensuring structured outputs align across different features and teams.