Language-agnostic AI knowledge registry for Technical Project Management, PRDs, PRD review, Software Architecture planning, Task breakdown, Estimation, Risk assessment, Status reporting, Backlog prioritization, Sprint planning, Retrospectives, and Agile ticket generation. Uses Markdown + Front-matter architecture.
95
97%
Does it follow best practices?
Impact
95%
1.03xAverage score across 10 eval scenarios
Passed
No known issues
Integration matrix: which skill connects to which and in what order.
A → B means: after A, B typically follows[gate] indicates mandatory approval gategraph TD
A[Feature Idea] --> B[Phase 1: Discovery]
B --> C[Phase 2: PRD Draft]
C --> D{PRD Approved?}
D -->|No| E[Phase 3: Review & Revise]
E --> C
D -->|Yes| F[Phase 4: Task Estimation]
F --> G[Phase 5: Ticket Generation]
G --> H{Tickets Approved?}
H -->|No| G
H -->|Yes| I[Phase 6: Sprint Placement]
I --> J{Sprint Confirmed?}
J -->|No| I
J -->|Yes| K[Ready for Development]graph TD
A[Task List / PRD] --> B["Phase 1: Estimation<br/>estimate-tasks"]
B --> C{Estimates Reviewed?}
C -->|No| B
C -->|Yes| D["Phase 2: Risk Assessment<br/>identify-risks"]
D --> E{Risks Accepted?}
E -->|No| D
E -->|Yes| F[Phase 3: Tracking Setup]
F --> G["Phase 4: Status Reporting<br/>generate-status-report"]
G --> H{Report Approved?}
H -->|No| G
H -->|Yes| I[Share with Stakeholders]create-prd → review-prd → [gate: PRD approved] → generate-tasks → estimate-tasks → identify-risks → prioritize-backlog → plan-tickets → plan-sprint → generate-status-report → create-retrospective| Next | When |
|---|---|
| review-prd | Always after PRD draft — review for completeness and feasibility |
| generate-tasks | After PRD reviewed and approved |
| plan-tickets | If tickets needed directly from PRD scope |
| Next | When |
|---|---|
| generate-tasks | After review passes (Approved or Approved with Suggestions) |
| create-prd | If review returns Needs Revision — loop back to re-draft |
| tech-lead | For deeper feasibility and estimation quality assessment |
| Next | When |
|---|---|
| estimate-tasks | To assign effort estimates to the task breakdown |
| plan-tickets | If the same initiative needs ticket drafts |
| Next | When |
|---|---|
| identify-risks | After estimation, to assess risks surfaced by high-uncertainty tasks |
| plan-sprint | To select tickets based on capacity vs estimates |
| Next | When |
|---|---|
| generate-status-report | Include the risk register in stakeholder status updates |
| plan-tickets | If risks reveal new ticket dependencies |
| plan-sprint | Scan sprint plan for dependency and capacity risks |
| Next | When |
|---|---|
| prioritize-backlog | After tickets drafted, rank them for sprint selection |
| (Create in tracker) | After ticket drafts approved |
| plan-sprint | Selected tickets feed into sprint planning |
| Next | When |
|---|---|
| plan-sprint | Use ordered backlog to select sprint candidates |
| plan-tickets | If newly prioritized items need ticket drafts |
| Next | When |
|---|---|
| generate-status-report | Report sprint progress to stakeholders |
| (Begin implementation) | Start working on sprint tickets |
| create-retrospective | After sprint ends, generate retrospective |
| Next | When |
|---|---|
| (Share with stakeholders) | After report approved |
| identify-risks | If report reveals new or escalating risks |
| create-retrospective | Status reports feed into end-of-sprint retrospective |
| Next | When |
|---|---|
| plan-sprint | Action items feed into the next sprint plan |
| project-manager | Feed action items into execution tracking |
Have a feature idea?
└─ create-prd → review-prd → generate-tasks → estimate-tasks
Need to prioritize?
└─ prioritize-backlog → plan-sprint
Need execution tracking?
└─ project-manager (agent)
└─ estimate-tasks → identify-risks → generate-status-report
Full end-to-end planning?
└─ product-owner (agent)
Need technical review?
└─ tech-lead (agent)
Full delivery cycle?
└─ delivery-lead (agent)
Sprint done?
└─ create-retrospective| Name | Type | Defined in | Purpose | | PRD Approved | gate | create-prd, product-owner, delivery-lead | Don't generate tasks without approved PRD | | Estimation Review | gate | estimate-tasks, project-manager | Don't proceed if >30% of tasks have low confidence | | Risk Acceptance | gate | identify-risks, project-manager | Every High/High risk must have an owner and plan | | Ticket Approved | gate | plan-tickets, product-owner | Don't create tracker issues without approval | | Status Report Approved | gate | generate-status-report, project-manager | Don't share report without approval | | Sprint Confirmed | gate | product-owner | Don't assume sprint placement | | Sprint Commitment | gate | plan-sprint, delivery-lead | Don't proceed without committed sprint plan | | Retrospective Complete | gate | create-retrospective, delivery-lead | Don't close cycle without action items |
docs
evals
scenario-1
scenario-2
scenario-3
scenario-4
scenario-5
scenario-6
scenario-7
scenario-8
scenario-9
scenario-10
skills
backlog
prioritize-backlog
ceremony
create-retrospective
plan-sprint
prd
create-prd
review-prd
task-management
estimate-tasks
generate-tasks
plan-tickets