specification-management
Initialize and manage specification directories with auto-incrementing IDs. Use when creating new specs, checking spec status, tracking user decisions, or managing the docs/specs/ directory structure. Maintains README.md in each spec to record decisions (e.g., PRD skipped), context, and progress. Orchestrates the specification workflow across PRD, SDD, and PLAN phases.
- License 许可
- MIT
- 最近更新
- 2026-11-01
- Stars
- ★ 3
- Forks
- 1
01 前言 Front Matter
- name
- specification-management
- description
- Initialize and manage specification directories with auto-incrementing IDs. Use when creating new specs, checking spec status, tracking user decisions, or managing the docs/specs/ directory structure. Maintains README.md in each spec to record decisions (e.g., PRD skipped), context, and progress. Orchestrates the specification workflow across PRD, SDD, and PLAN phases.
- allowed-tools
- Read, Write, Edit, Bash, TodoWrite, Grep, Glob
02 资源文件 3
- 参考文档readme-template.md769 B
- 参考文档reference.md2.8 KB
- 脚本spec.py7.4 KB
03 SKILL.md 正文
Specification Management Skill
You are a specification workflow orchestrator that manages specification directories and tracks user decisions throughout the PRD → SDD → PLAN workflow.
When to Activate
Activate this skill when you need to:
- Create a new specification directory with auto-incrementing ID
- Check specification status (what documents exist)
- Track user decisions (e.g., "PRD skipped because requirements in JIRA")
- Manage phase transitions (PRD → SDD → PLAN)
- Initialize or update README.md in spec directories
- Read existing spec metadata via spec.py
Core Responsibilities
1. Directory Management
Use spec.py to create and read specification directories:
# Create new spec (auto-incrementing ID)
~/.claude/plugins/marketplaces/the-startup/plugins/start/skills/specification-lifecycle-management/spec.py "feature-name"
# Read existing spec metadata (TOML output)
~/.claude/plugins/marketplaces/the-startup/plugins/start/skills/specification-lifecycle-management/spec.py 004 --read
# Add template to existing spec
~/.claude/plugins/marketplaces/the-startup/plugins/start/skills/specification-lifecycle-management/spec.py 004 --add product-requirements
TOML Output Format:
id = "004"
name = "feature-name"
dir = "docs/specs/004-feature-name"
[spec]
prd = "docs/specs/004-feature-name/product-requirements.md"
sdd = "docs/specs/004-feature-name/solution-design.md"
files = [
"product-requirements.md",
"solution-design.md"
]
2. README.md Management
Every spec directory should have a README.md tracking decisions and progress.
Create README.md when a new spec is created:
# Specification: [ID]-[name]
## Status
| Field | Value |
|-------|-------|
| **Created** | [date] |
| **Current Phase** | Initialization |
| **Last Updated** | [date] |
## Documents
| Document | Status | Notes |
|----------|--------|-------|
| product-requirements.md | pending | |
| solution-design.md | pending | |
| implementation-plan.md | pending | |
**Status values**: `pending` | `in_progress` | `completed` | `skipped`
## Decisions Log
| Date | Decision | Rationale |
|------|----------|-----------|
## Context
[Initial context from user request]
---
*This file is managed by the specification-lifecycle-management skill.*
Update README.md when:
- Phase transitions occur (start, complete, skip)
- User makes workflow decisions
- Context needs to be recorded
3. Phase Transitions
Guide users through the specification workflow:
- Check existing state - Use
spec.py [ID] --read - Suggest continuation point based on existing documents:
- If
planexists: "PLAN found. Proceed to implementation?" - If
sddexists butplandoesn't: "SDD found. Continue to PLAN?" - If
prdexists butsdddoesn't: "PRD found. Continue to SDD?" - If no documents: "Start from PRD?"
- If
- Record decisions in README.md
- Update phase status as work progresses
4. Decision Tracking
Log all significant decisions:
## Decisions Log
| Date | Decision | Rationale |
|------|----------|-----------|
| 2025-12-10 | PRD skipped | Requirements documented in JIRA-1234 |
| 2025-12-10 | Start with SDD | Technical spike already completed |
Workflow Integration
This skill works with document-specific skills:
product-requirementsskill - PRD creation and validationsolution-designskill - SDD creation and validationimplementation-planskill - PLAN creation and validation
Handoff Pattern:
- Specification-management creates directory and README
- User confirms phase to start
- Context shifts to document-specific work
- Document skill activates for detailed guidance
- On completion, context returns here for phase transition
Validation Checklist
Before completing any operation:
- [ ] spec.py command executed successfully
- [ ] README.md exists and is up-to-date
- [ ] Current phase is correctly recorded
- [ ] All decisions have been logged
- [ ] User has confirmed next steps
Output Format
After spec operations, report:
📁 Specification: [ID]-[name]
📍 Directory: docs/specs/[ID]-[name]/
📋 Current Phase: [Phase]
Documents:
- product-requirements.md: [status]
- solution-design.md: [status]
- implementation-plan.md: [status]
Recent Decisions:
- [Decision 1]
- [Decision 2]
Next: [Suggested next step]
04 同仓库更多 Skills
seedance-prompt-en
Write effective prompts for Jimeng Seedance 2.0 multimodal AI video generation. Use when users want to create video prompts using text, images, videos, and audio inputs with the @ reference system. Covers camera movements, effects replication, video extension, editing, music beat-matching, e-commerce ads, short dramas, and educational content.
onepage-pdf
Convert an HTML page into a single continuous-page PDF (one tall page, no pagination breaks), preserving desktop layout, backgrounds and selectable text. Use when the user asks to turn an HTML file/report/proposal into a "single-page PDF", "long PDF", "不分页 PDF", "单页 PDF", "长图式 PDF", or complains that an HTML-to-PDF export breaks into pages or cuts content. Supports optional string redaction with leak verification.
native-feel-cross-platform-desktop
Use when the user is designing, prototyping, or rewriting a desktop app that must run on multiple OSes (macOS + Windows, optionally Linux) AND feel indistinguishable from a native app to its users — fast launch, native windowing, native input handling, native materials. Trigger words include "cross-platform desktop", "Electron alternative", "Tauri vs native", "WebView wrapper", "near-native performance", "Raycast architecture", "WebKit/WebView2 quirks", "WKWebView", "system tray app", "global hotkey app", "launcher app". Do NOT trigger this skill for pure web apps, pure mobile apps, or for greenfield projects that have no native-feel requirement.
gstack
Router for the gstack skill suite. (gstack)
fireworks-tech-graph
Use when the user wants to create any technical diagram - architecture, data flow, flowchart, sequence, agent/memory, or concept map - and export as SVG+PNG. Trigger on: "画图" "帮我画" "生成图" "做个图" "架构图" "流程图" "可视化一下" "出图" "generate diagram" "draw diagram" "visualize" or any system/flow description the user wants illustrated.
dbs-video-extract
接收抖音、小红书、微信视频号等短视频链接或分享文案,查询作品/账号数据并提取语音文字稿,按作者和标题归档为 Markdown。用户希望完整解析短视频、取得数据或文字稿时使用;运行前检查 TikHub 与轻抖使用凭证,缺少时用新手能理解的方式引导购买和安全配置。