spec-author

Convert vague product ideas and bug reports into implementation-ready specifications.

2|1|Updated Jul 25, 2026
One-click install
npx skills add https://github.com/CODE-SAURABH/OpenSkills --skill spec-author-code-saurabh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec-author
Source: https://github.com/CODE-SAURABH/OpenSkills/tree/main/spec-author
Command: npx skills add https://github.com/CODE-SAURABH/OpenSkills --skill spec-author-code-saurabh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill transforms vague product ideas, bug reports, and change requests into precise specifications that engineering teams can implement without guesswork.

Core Features & Use Cases

  • Intent Extraction: Clarifies the underlying problem, affected actors, desired outcomes, and unresolved questions before proposing a solution.
  • Scope and Technical Analysis: Defines inclusions, exclusions, dependencies, effort, implementation constraints, risks, and relevant existing code.
  • Implementation-Ready Documentation: Produces structured requirements, user stories, acceptance criteria, test plans, security considerations, and definition-of-done checklists.
  • Use Case: When a stakeholder requests a new dashboard capability, use this Skill to validate the problem, inspect the codebase, define the feature boundary, and create a reviewable specification suitable for a GitHub issue.

Quick Start

Use the spec-author skill to turn this feature idea into an implementation-ready specification, asking up to three high-value clarification questions before drafting.

Frequently Asked Questions about spec-author

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

FAQPage Schema
How do I turn a vague product idea into implementation-ready technical specifications?

To turn a vague idea into implementation-ready specifications, extract the underlying intent, define the scope, analyze the codebase, and draft structured requirements with acceptance criteria and test plans.

What is the best way to write acceptance criteria for GitHub issues from feature requests?

Writing acceptance criteria for GitHub issues requires clarifying desired outcomes, defining feature boundaries, and producing structured documentation including user stories and a definition-of-done checklist.

How does codebase analysis improve technical documentation for new features?

Codebase analysis improves technical documentation by identifying relevant existing code, implementation constraints, and dependencies, ensuring the generated specifications align with current architecture and risks.

Can I use this approach to process bug reports into engineering change documentation?

Yes, you can process bug reports into engineering change documentation by extracting the core problem, defining exclusions, and drafting structured requirements suitable for engineering review.

What are the limitations of automated requirement drafting for backlog items?

Automated requirement drafting for backlog items requires sequential intent extraction and may ask up to three high-value clarification questions to resolve ambiguities before generating the specification.