菜单
Planning document lifecycle management. Use when implementing features from plans, updating planning document status, moving completed plans, or managing cross-references between plans.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Backend API development with Express, Zod validation, permissions, and security. Use when creating or modifying API endpoints, adding route handlers, implementing validation, or working with authentication/authorization.
Query and analyze production logs via BetterStack MCP. Use when diagnosing production issues, investigating errors, analyzing patterns, or monitoring system health.
Code quality standards, complexity management, and anti-over-engineering. Use when reviewing code, implementing features, or ensuring quality standards. Covers complexity limits, linting, and simplicity principles.
Documentation standards and decision criteria. Use when deciding whether to document, creating documentation, or maintaining existing docs. Covers significance thresholds, structure, and cross-referencing.
Git commit workflow and standards. Use when committing code, batching changes, or verifying builds before commits. Covers build verification, commit message format, and quality gates.
Debug local development issues by analyzing logs, checking processes, and diagnosing errors. Use when servers won't start, errors occur, or behavior is unexpected.
| name | plan-lifecycle |
| description | Planning document lifecycle management. Use when implementing features from plans, updating planning document status, moving completed plans, or managing cross-references between plans. |
Standards for managing planning documents through their lifecycle.
Upcoming → Current → Completed
| Status | Location |
|---|---|
| Upcoming | documentation/planning/upcoming/ |
| Current | documentation/planning/current/ |
| Completed | documentation/planning/completed/ |
Update planning documents continuously:
- [x] ✅ Create user model - Commit: abc123f
- [x] ✅ Add API endpoints - Commit: def456a
- [ ] Implement frontend form
**Implementation Notes**:
- Chose Passport.js for OAuth due to security maintenance
- Added Redis caching for session performance
- See `documentation/technical/auth/` for patterns
When all phases complete:
## Completion Summary
**Completed**: [Date]
**Final Commit**: [hash]
### Results
- [Key outcomes and deliverables]
### Lessons Learned
- [Insights for future work]
### Follow-up Tasks
- [Any identified follow-up work]
Change the Status field:
**Status**: Completed <!-- was: Current -->
mv documentation/planning/current/[plan].md \
documentation/planning/completed/[plan].md
Check other planning documents that reference this plan:
Commit must include:
git add documentation/planning/
git commit -m "docs: complete [feature] implementation - move plan to completed"
## Implementation Progress
### Phase 1: [Name]
**Status**: ✅ Complete | 🔄 In Progress | ⏳ Pending
**Started**: [Date]
**Completed**: [Date]
**Actions**:
- [x] ✅ Action 1 - [Notes]
- [x] ✅ Action 2 - [Notes]
- [ ] Action 3
### Phase 2: [Name]
**Status**: ⏳ Pending
...
Before marking any phase complete:
Before marking plan complete:
documentation/planning/current/ - Active plansdocumentation/planning/completed/ - Finished plansdocumentation/planning/upcoming/ - Future plansdocumentation/workflow/planning-template.md - Plan template