skills.rest
outcomeeng
outcomeengOFFICIAL
Explore all skills by this author →
WebsiteGitHub

managing-specs

Enforce canonical specs/ directory structure, templates, and naming conventions.

1|Updated Jan 6, 2026
Search Tags:#templates#adr#prd#specs#work-items#trd#pdr
One-click install
npx skills add https://github.com/outcomeeng/claude --skill managing-specs-outcomeeng
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: managing-specs
Source: https://github.com/outcomeeng/claude/tree/main/plugins/specs/skills/managing-specs
Command: npx skills add https://github.com/outcomeeng/claude --skill managing-specs-outcomeeng

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

ALWAYS invoke this skill when creating or organizing specs, capabilities, features, stories, or ADRs. NEVER create, read, or modify any files in the specs/ directory without this skill.

Core Features & Use Cases

  • Canonical specs/ directory structure and templates (PRD/TRD, ADR/PDR, and work item patterns) that ensure consistency across products.
  • Template access, auditing, and enforcement of naming conventions and directory layout.
  • Guidance for creating and auditing work items (capabilities, features, stories) with BSP numbering, ADR/PDR links, and template placement.

Quick Start

Invoke this skill to establish or reorganize the specs/ directory according to the SPX framework standards.

Frequently Asked Questions about managing-specs

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

FAQPage Schema
How do I standardize specs directory structure for PRD and TRD templates?▼

Standardize specs directory structure by enforcing a canonical layout for PRD, TRD, and work items. This provides a single source of truth, ensuring consistent naming conventions and template placement across product teams.

What is the best way to manage ADR and PDR files in a product specs repository?▼

Manage ADR and PDR files by co-locating them within a canonical specs directory. Enforcing immutable templates and naming conventions ensures decisions and requirements remain organized and auditable across the project.

How do I organize capability, feature, and story hierarchies in specs?▼

Organize capability, feature, and story hierarchies by applying enforced work-item rules and BSP numbering. This structure links directly to ADR and PDR documents, maintaining a clear hierarchy from product requirements to implementation.

Do I need SPX framework requirements to enforce work-item rules and BSP numbering?▼

SPX framework requirements are satisfied by applying immutable templates, work-item rules, and BSP numbering. This enforces the canonical specs directory structure and ensures compliance with the framework's standards.

When should I not modify files in the specs directory?▼

You should not modify files in the specs directory without an enforcing skill to maintain a single source of truth. Bypassing the canonical structure risks breaking naming conventions, BSP numbering, and template immutability.

Related Skills

Explore More Product & Management Skills→
gotalabgotalab
3.6k

kiro-spec-init

Scaffold spec.json and requirements.md from templates in a KIRO-managed specs directory.

Community
Intermediate
simonheimlichersimonheimlicher
1

managing-specs

Create and organize SPX specs with structured templates and BSP numbering.

Community
Basic
outcomeengineeringoutcomeengineering
1

managing-specs

Create and organize project specifications with templates in the specs/ directory.

Official
Advanced
allaydesaiallaydesai
2

bmad-create-epics-and-stories

Convert product requirements and architecture documents into Markdown epics and user stories.

Community
Advanced