lmiranda
2d51df7a42
Phase 1b: Rename all ~94 commands across 12 plugins to /<noun> <action> sub-command pattern. Git-flow consolidated from 8→5 commands (commit variants absorbed into --push/--merge/--sync flags). Dispatch files, name: frontmatter, and cross-reference updates for all plugins. Phase 2: Design documents for 8 new plugins in docs/designs/. Phase 3: Scaffold 8 new plugins — saas-api-platform, saas-db-migrate, saas-react-platform, saas-test-pilot, data-seed, ops-release-manager, ops-deploy-pipeline, debug-mcp. Each with plugin.json, commands, agents, skills, README, and claude-md-integration. Marketplace grows from 12→20. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
1.4 KiB
1.4 KiB
description
| description |
|---|
| Risk register template and management conventions for project planning |
Risk Register
Wiki Page
Page name: Risk-Register: {Name} (e.g., Risk-Register: Driving School SaaS)
Dependency Header
> **Project:** {Name}
> **Sprint:** N/A (project-level, reviewed per sprint)
> **Issues:** N/A
> **Parent:** Project: {Name}
> **Created:** YYYY-MM-DD
> **Status:** Active | Archived
Risk Register Template
| ID | Risk | Probability | Impact | Score | Mitigation | Owner | Status |
|---|---|---|---|---|---|---|---|
| R1 | Example risk description | Medium | High | 6 | Mitigation strategy | Dev | Open |
Scoring
| Probability | Value |
|---|---|
| Low | 1 |
| Medium | 2 |
| High | 3 |
| Impact | Value |
|---|---|
| Low | 1 |
| Medium | 2 |
| High | 3 |
Score = Probability x Impact (1-9 range)
Risk Lifecycle
| Status | Meaning |
|---|---|
| Open | Active risk, mitigation planned |
| Monitoring | Risk identified but not yet actionable |
| Mitigated | Mitigation applied, risk reduced |
| Occurred | Risk materialized — track resolution |
| Closed | No longer relevant |
Integration
/project plancreates initial risk register/project statussummarizes open risk count and top-3 by score/sprint closeupdates risk statuses in lessons learned