spec-authoring

Generate structured product, technical, and operational specifications from feature concepts.

Updated Mar 22, 2026
One-click install
npx skills add https://github.com/patrickrmoore/sdd-test --skill spec-authoring-patrickrmoore
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec-authoring
Source: https://github.com/patrickrmoore/sdd-test/tree/main/.github/skills/spec-authoring
Command: npx skills add https://github.com/patrickrmoore/sdd-test --skill spec-authoring-patrickrmoore

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) and references (resource) components.

What problem does it solve?

Writes structured specifications (product, technical, and operational) from a feature description, enabling clear alignment, traceability, and shared understanding across teams.

Core Features & Use Cases

  • Parse a feature description and determine spec_type from frontmatter or defaults.
  • Generate a complete spec draft using the provided templates (assets/spec-template.md).
  • Support NEEDS CLARIFICATION markers and produce ready-to-publish documentation.

Quick Start

Provide a feature concept and context to generate a full specification draft.

Frequently Asked Questions about spec-authoring

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

FAQPage Schema
How do I write a structured PRD from a feature concept?

To write a structured PRD from a feature concept, provide the feature description and context to generate a full specification draft using standardized templates, ensuring clear alignment, traceability, and shared understanding across teams.

What is the best way to resolve ambiguity in user stories during specification drafting?

Resolving ambiguity in user stories requires inserting NEEDS CLARIFICATION markers directly into the specification draft, highlighting missing requirements so teams can address gaps before publishing the documentation.

Can I generate technical and operational specifications, or is this limited to product requirements?

You can generate technical and operational specifications alongside product requirements. The tooling parses frontmatter to determine the spec type, applying templates across multiple domains to handle integration points and success criteria.

Do I need to provide specific frontmatter fields to enforce mandatory sections in my specification?

Yes, providing specific frontmatter fields is required to enforce mandatory sections in your specification. The system satisfies requirements for mandatory frontmatter inputs to drive template-based drafting and ensure measurable success criteria are included.

How does a specification template handle integration points and success criteria?

A specification template handles integration points and success criteria by enforcing mandatory sections within the document structure. This ensures the final deliverable includes measurable success criteria and clear integration mapping.