managing-specs

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

1|Updated Jan 6, 2026
One-click install
npx skills add https://github.com/outcomeengineering/spx-claude --skill managing-specs-outcomeengineering
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: managing-specs
Source: https://github.com/outcomeengineering/spx-claude/tree/main/plugins/specs/skills/managing-specs
Command: npx skills add https://github.com/outcomeengineering/spx-claude --skill managing-specs-outcomeengineering

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill provides a standardized framework for creating and managing all project specifications, including requirements, decisions, and work items, ensuring consistency and clarity across your projects.

Core Features & Use Cases

  • Template Access: Easily locate and use templates for various specification documents (PRDs, TRDs, ADRs, PDRs, Capabilities, Features, Stories).
  • Structure Definition: Understand and implement the specs/ directory hierarchy for organized project documentation.
  • Work Item Management: Learn how to create, number, and track the status of capabilities, features, and stories.
  • Use Case: When starting a new feature, use this Skill to access the correct template for a feature specification, define its requirements, and structure its associated stories and tests according to best practices.

Quick Start

Use the managing-specs skill to read the template for creating a new feature specification.

Frequently Asked Questions about managing-specs

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

FAQPage Schema
How do I structure project specifications and requirements documentation in a single directory?

To structure project specifications, use a standardized `specs/` directory hierarchy that organizes capabilities, features, stories, and decision records into a single source of truth. This framework defines exactly where each specification document should reside.

What templates are available for writing technical requirements and decision records?

Available templates include Product Requirements Documents (PRDs), Technical Requirements Documents (TRDs), Architecture Decision Records (ADRs), Preliminary Design Reviews (PDRs), as well as templates for capabilities, features, and stories.

How do I number and track work items like capabilities and features?

You number and track work items using BSP numbering. This system facilitates structured documentation by assigning unique identifiers to capabilities, features, and stories, allowing you to monitor their status throughout the project lifecycle.

What is the best way to co-locate tests with feature specifications?

The best way to co-locate tests with feature specifications is to follow the defined `specs/` directory structure, which integrates test files directly alongside their corresponding stories and requirements documentation.

When do I need an Architecture Decision Record versus a Product Requirements Document?

You need an Architecture Decision Record (ADR) to document specific technical decisions and their rationale, whereas a Product Requirements Document (PRD) defines the overall product goals, capabilities, and feature requirements for a project.