skills.rest
alexandremendoncaalvaro
alexandremendoncaalvaroCOMMUNITY
Explore all skills by this author →
Website𝕏@xambitoGitHub

ad-spec

Draft feature specifications with User Scenarios, Requirements, and Success Criteria.

728|16|Updated Mar 9, 2026
Search Tags:#workflow#documentation#adr#spec#prd#feature-spec
One-click install
npx skills add https://github.com/alexandremendoncaalvaro/CorridorKey-Runtime --skill ad-spec
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ad-spec
Source: https://github.com/alexandremendoncaalvaro/CorridorKey-Runtime/tree/main/.agents/skills/ad-spec
Command: npx skills add https://github.com/alexandremendoncaalvaro/CorridorKey-Runtime --skill ad-spec

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Draft a feature-level specification at doc/specs/0001-ad-spec.md following the six-layer artifact stack (Constitution → Domain → Product → Spec → Plan/Decisions → Code). Adapts GitHub Spec Kit's mandatory sections (User Scenarios, Requirements, Success Criteria) to the kit's documentation discipline. Use when the user wants to write, draft, scaffold, or open a feature spec, feature brief, user stories, or success criteria for one feature. Product-level scoping (PRD, multi-feature roadmap, target user, product success metrics) belongs to ad-prd (Layer 3).

Core Features & Use Cases

Draft a feature spec for a single feature that captures context, scenarios, functional and non-functional requirements, success criteria, edge cases, and decisions. The spec should align with the six-layer artifact stack and enable downstream ADRs, tasks, and PRD inheritance.

  • Aligns feature-level work to Domain language and product strategy.
  • Enables traceable path from spec to implementation via ADRs and tasks.

Quick Start

Create a new spec file at doc/specs/0001-ad-spec.md for your feature by supplying its title and key context.

Frequently Asked Questions about ad-spec

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

FAQPage Schema
How do I draft a feature spec with user scenarios and success criteria?▼

To draft a feature spec, you write a document at doc/specs/0001-ad-spec.md following a six-layer artifact stack and Spec Kit-aligned sections, capturing user scenarios, functional requirements, and success criteria for a single feature.

What is the six-layer artifact stack for feature specification?▼

The six-layer artifact stack for feature specification is a documentation discipline structured as Constitution, Domain, Product, Spec, Plan or Decisions, and Code, ensuring traceable alignment from domain language down to implementation.

How do I write functional and non-functional requirements for a feature brief?▼

You write functional and non-functional requirements by scaffolding a feature spec file that captures context, edge cases, and decisions, aligning the requirements with product-domain language and enabling downstream ADRs and task linkage.

When should I write a feature spec instead of a product requirements document?▼

You write a feature spec when documenting a single feature's scenarios and success criteria, whereas a product requirements document belongs to product-level scoping like multi-feature roadmaps, target users, and product success metrics.

Does this feature spec workflow support PRD inheritance and ADR linkage?▼

Yes, the feature spec workflow supports PRD inheritance by aligning feature-level work to product strategy, and it enables a traceable path to implementation through architecture decision records and linked tasks.

Can I use this spec workflow for multi-feature roadmap planning?▼

No, this spec workflow is designed for writing a single feature specification with user scenarios and requirements, while multi-feature roadmap planning and target user definitions belong to the product-level PRD layer.

Related Skills

Explore More Product & Management Skills→
alexandremendoncaalvaroalexandremendoncaalvaro
728

ad-prd

Create and maintain product-level PRD documents with lifecycle statuses and linked ADRs.

Community
Advanced
2lab-ai2lab-ai
36

spec

Generate a formal feature spec with decision gates and changelog.

Official
Advanced
ljucaskljucask
1

pm-glossary

Generate and update structured project glossaries with categorized terms and relationships.

Community
Intermediate
eugenelimeugenelim
15

receive-brief

Break multi-feature product briefs into shippable specs and delivery slices.

Community
Advanced