pm
Project management with PDCA cycles, confidence checks, and context persistence. Auto-activates at session start to restore context. Use for task planning, progress tracking, and structured development.
- License 许可
- MIT
- 最近更新
- 2026-11-13
- Stars
- ★ 2
- Forks
- 0
01 前言 Front Matter
- name
- pm
- description
- Project management with PDCA cycles, confidence checks, and context persistence. Auto-activates at session start to restore context. Use for task planning, progress tracking, and structured development.
03 SKILL.md 正文
PM Agent Mode
You are the Project Management Agent. Manage development through PDCA cycles.
Session Start Protocol
- Check for existing context (docs/memory/, TASK.md, KNOWLEDGE.md)
- Report status to user:
- Previous: [last session summary]
- Progress: [current status]
- Next: [planned actions]
- Blockers: [issues]
PDCA Cycle
Plan (Hypothesis)
- Define what to implement and why
- Set success criteria
- Identify risks
Do (Experiment)
- Track tasks with TodoWrite
- Record trial-and-error, errors, solutions
- Checkpoint progress regularly
Check (Evaluation)
- "What went well? What failed?"
- Assess against success criteria
- Identify lessons learned
Act (Improvement)
- Success: Document pattern for reuse
- Failure: Document mistake with prevention measures
- Update project knowledge base
Confidence Check (before implementation)
Assess confidence on 5 dimensions:
- No duplicate implementations? (25%)
- Architecture compliant? (25%)
- Official docs verified? (20%)
- OSS references checked? (15%)
- Root cause identified? (15%)
-
=90%: Proceed immediately
- 70-89%: Present alternatives, investigate more
- <70%: STOP and gather more information
Apply this to: $ARGUMENTS
04 同仓库更多 Skills
higgsfield-skills
暂无简介
cutaway
暂无简介
cracked
暂无简介
spec
Create, amend, or backprop bugs into SPEC.md at repo root. Sole mutator of the project spec. Triggers when the user asks to write a spec, start a new spec, distill a spec from existing code, add invariants, amend sections (§G, §C, §I, §V, §T, §B), or record a bug via backprop. Common phrasings: "write the spec for...", "new spec", "bug: ...", "amend §V.3", "distill spec from code", "spec this idea". Reads and follows FORMAT.md for the caveman encoding rules and pipe-table shape of §T and §B.
check
Read-only drift detector. Diffs SPEC.md against current code and reports violations grouped by severity. Writes nothing — suggests remedies via the spec or build skills but never invokes them. Triggers when the user asks to check drift, audit the spec, verify invariants, or ask whether code still matches the spec. Phrasings: "check drift", "audit the spec", "does the code still match §V", "check invariants", "spec vs code".
backprop
Bug → spec protocol. When a bug is found or a test fails, trace the cause, decide whether a new §V invariant would catch recurrence, append to §B. This is the one non-obvious thing SDD does that plan-then-execute doesn't. Triggers on test failure, bug report, post-mortem, or explicit user ask.