skills.rest
bennybennison
bennybennisonCOMMUNITY
Explore all skills by this author →
GitHub

spec-lifecycle

Organize specifications into a hierarchical lifecycle from epics to tasks.

Updated Apr 11, 2026
Search Tags:#workflow#documentation#specification#feature#lifecycle#epic#task
One-click install
npx skills add https://github.com/bennybennison/agent-toolkit --skill spec-lifecycle-bennybennison
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: spec-lifecycle
Source: https://github.com/bennybennison/agent-toolkit/tree/main/skills/spec-lifecycle
Command: npx skills add https://github.com/bennybennison/agent-toolkit --skill spec-lifecycle-bennybennison

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It provides a consistent, hierarchical process for creating, tracking, and evolving specifications—from high‑level epics down to concrete tasks—ensuring alignment across product, engineering, and governance.

Core Features & Use Cases

  • Hierarchical Spec Framework: Organize work into Epics, Feature Specs, Stories, and Tasks with clear ownership.
  • Lifecycle State Management: Move specs through Draft, Active, Complete, and Deprecated states with defined transition criteria.
  • Cross‑Referencing & Alignment: Enforce naming conventions, dashboards, and verification checklists to keep specs, code, and documentation in sync.
  • Use Case Example: When starting a new order processing feature, the skill guides you to create the feature spec, break it into stories, and track each task to completion.

Quick Start

Create a new feature spec for the order processing pipeline using the spec-lifecycle skill.

Frequently Asked Questions about spec-lifecycle

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

FAQPage Schema
How do I break down a large epic into actionable development tasks?▼

Specifications move through Draft, Active, Complete, and Deprecated states with defined transition criteria. This lifecycle state management ensures specs meet governance requirements before implementation begins.

What is the best way to keep feature specs aligned with code and documentation?▼

Keep feature specs aligned by enforcing naming conventions, dashboards, and verification checklists for cross-referencing. This maintains synchronization between specifications, code, and documentation throughout the lifecycle.

How do I structure a new feature specification for an order processing pipeline?▼

Structure a new feature specification by creating the feature spec, breaking it into stories, and tracking each task to completion. Follow defined formats and cross-referencing rules to meet governance requirements.

Can I track status and ownership across epics, features, stories, and tasks?▼

Yes, you can track status and ownership across epics, feature specs, stories, and tasks. The hierarchical framework provides clear ownership and state transitions to monitor alignment throughout development.

Related Skills

Explore More Product & Management Skills→
DenissvgnDenissvgn

product-owner

Clarify Product Owner responsibilities and validate product vision against business goals.

Community
Basic
yuboonyuboon
5

openspec-onboard

Guide users through the complete OpenSpec workflow cycle from task selection to archiving.

Community
Advanced
Long-NguyenHaiLong-NguyenHai

deployment-patterns

Provide deployment guidelines for CI/CD pipelines, Docker containerization, and rollback strategies.

Community
Advanced
daymadedaymade
1.3k

docs-cleaner

Consolidate redundant documentation files into a single source of truth.

Community
Advanced