skills.rest
csackrider
csackriderCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

spec-management

Organizes feature specs and ADRs using standardized templates and naming conventions.

1|Updated Apr 28, 2026
Search Tags:#planning#templates#documentation#adr#tech-spec#product-spec#spec-management
One-click install
npx skills add https://github.com/csackrider/AI-DLC --skill spec-management-csackrider
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: spec-management
Source: https://github.com/csackrider/AI-DLC/tree/main/plugins/ai-dlc-skills/skills/spec-management
Command: npx skills add https://github.com/csackrider/AI-DLC --skill spec-management-csackrider

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Organizations need a consistent, structured way to create, update, and reference feature specifications and architecture decisions across planning, design, and delivery.

Core Features & Use Cases

  • Templates for Product Spec, Tech Spec, and ADRs to standardize artifacts across planning, design, and decision recording.
  • Clear guidance on naming conventions, relationships between specs, and lifecycle management.
  • Support for linking related specs and ADRs to maintain traceability across teams and timelines.

Quick Start

Create a new feature folder and populate feature/<slug>/product-spec.md, feature/<slug>/tech-spec.md, and adr/NNNN-*.md using the provided templates.

Frequently Asked Questions about spec-management

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

FAQPage Schema
What are product specs, tech specs, and ADRs used for in software development?▼

Product specs, tech specs, and ADRs standardize feature planning, technical design, and architecture decisions. They provide a consistent structure for documenting software requirements and recording governance decisions across planning, design, and delivery workflows.

How do I create standardized feature specifications and architecture decision records?▼

Create standardized feature specifications by setting up a feature folder and populating product-spec.md, tech-spec.md, and adr/NNNN-*.md files using provided templates. This organizes artifacts and maintains naming conventions across your project.

How do architecture decision records fit into the software feature specification lifecycle?▼

Architecture decision records fit into the specification lifecycle by linking related specs and ADRs to maintain traceability. This connects feature planning and design with governance decisions across teams and timelines.

Do I need any specific frameworks or dependencies to start managing software specs with templates?▼

No specific frameworks or dependencies are required to start managing software specs. You can immediately create feature directories and populate standardized markdown templates for product specs, tech specs, and ADRs.

What's the best way to organize and link multiple feature specs and architecture decisions?▼

The best way to organize and link feature specs and architecture decisions is using standardized naming conventions and a structured folder hierarchy. This maintains traceability and clear relationships between related product specs, tech specs, and ADRs.

Related Skills

Explore More Product & Management Skills→
jikig-aijikig-ai
12

spec-templates

Generate spec.md, tasks.md, and component.md templates with frontmatter fields.

Official
Basic
endaomentendaoment

spec-and-plan

Convert free-form feature descriptions into technical specs and tracking issues.

Official
Intermediate
warpdotdevwarpdotdev
292

spec-driven-implementation

Enforce product and tech specs before implementation in source control.

Official
Intermediate
heltondoriaheltondoria
1

feature-spec

Generate implementation specifications from PRD features with API contracts and test scenarios.

Community
Advanced