Math Product Management
Strategic product thinking applied to formal verification projects. While math-project-management handles execution (schedules, tasks, milestones), this skill handles strategy (what to build, for whom, why, and in what order).
Routing
- USE FOR: Product management for mathematical formalization projects — roadmap creation, stakeholder management, feature prioritization for formal verification artifacts, theorem portfolio management, release planning, and the business/academic value analysis of formal proofs. Complements math-project-management (scheduling/execution) with strategic product thinking.
- DO NOT USE FOR: project-level scheduling (use @math-project-management); strategy methodology (use @applied-strategy-analysis); engineering discipline view (use @applied-engineering-disciplines).
- TRIGGERS: product management, roadmap, stakeholder management, feature prioritization, formal verification PM.
Workflow
- Frame the product question: roadmap, prioritisation, stakeholder communication, or scope decision.
- Pick the matching template; identify data inputs needed (theorem counts, dependency graph, coverage matrix).
- Produce the artifact (roadmap, RICE table, stakeholder brief).
- Hand off: to
@math-project-management for scheduling, to @lean-retro-methodology for retro-driven re-prioritisation, to @lean-zettelkasten.
Recovery & STOP
- STOP if the question is operational scheduling — delegate to
@math-project-management.
- STOP if a strategic-analysis lens dominates — delegate to
@applied-strategy-analysis.
- STOP if data inputs are missing — escalate to audit / blueprint skills first.
Handoffs
- Predecessors:
agent:gateway, skill:lean-research.
- Successors:
skill:math-project-management, skill:lean-retro-methodology, skill:lean-zettelkasten.
Detailed reference
Full content for math-product-management lives in
references/math-product-management-handbook.md.
Load that file when the skill is convened; the SKILL.md only carries
the dispatch contract and the parts index.
| Section |
Topic |
| Part 1 |
Product vs. Project Management |
| Part 2 |
Theorem Portfolio Management |
| Part 3 |
Stakeholder Analysis |
| Part 4 |
Roadmap Planning |
| Part 5 |
Value Analysis |
| Part 6 |
Decision Frameworks |
| Part 7 |
Metrics and Analytics |
| Part 8 |
Cross-References |
See also
1---2name: math-product-management3description: USE FOR: Product management for mathematical formalization projects — roadmap creation, stakeholder management, feature prioritization for formal verification artifacts, theorem portfolio management, release planning, and the business/academic value analysis of formal proofs. Complements math-project-management (scheduling/execution) with strategic product thinking. DO NOT USE FOR: project-level scheduling (use @math-project-management); strategy methodology (use @applied-strategy-analysis); engineering discipline view (use @applied-engineering-disciplines). TRIGGERS: product management, roadmap, stakeholder management, feature prioritization, formal verification PM.4---567# Math Product Management89Strategic product thinking applied to formal verification projects. While math-project-management handles execution (schedules, tasks, milestones), this skill handles strategy (what to build, for whom, why, and in what order).1011---1213## Routing1415- **USE FOR:** Product management for mathematical formalization projects — roadmap creation, stakeholder management, feature prioritization for formal verification artifacts, theorem portfolio management, release planning, and the business/academic value analysis of formal proofs. Complements math-project-management (scheduling/execution) with strategic product thinking.16- **DO NOT USE FOR:** project-level scheduling (use @math-project-management); strategy methodology (use @applied-strategy-analysis); engineering discipline view (use @applied-engineering-disciplines).17- **TRIGGERS:** product management, roadmap, stakeholder management, feature prioritization, formal verification PM.1819## Workflow20211. Frame the product question: roadmap, prioritisation, stakeholder communication, or scope decision.222. Pick the matching template; identify data inputs needed (theorem counts, dependency graph, coverage matrix).233. Produce the artifact (roadmap, RICE table, stakeholder brief).244. Hand off: to `@math-project-management` for scheduling, to `@lean-retro-methodology` for retro-driven re-prioritisation, to `@lean-zettelkasten`.2526## Recovery & STOP2728- STOP if the question is operational scheduling — delegate to `@math-project-management`.29- STOP if a strategic-analysis lens dominates — delegate to `@applied-strategy-analysis`.30- STOP if data inputs are missing — escalate to audit / blueprint skills first.3132## Handoffs3334- **Predecessors:** `agent:gateway`, `skill:lean-research`.35- **Successors:** `skill:math-project-management`, `skill:lean-retro-methodology`, `skill:lean-zettelkasten`.3637---3839## Detailed reference4041Full content for `math-product-management` lives in42[`references/math-product-management-handbook.md`](../../references/math-product-management-handbook.md).43Load that file when the skill is convened; the SKILL.md only carries44the dispatch contract and the parts index.4546| Section | Topic |47|---|---|48| Part 1 | Product vs. Project Management |49| Part 2 | Theorem Portfolio Management |50| Part 3 | Stakeholder Analysis |51| Part 4 | Roadmap Planning |52| Part 5 | Value Analysis |53| Part 6 | Decision Frameworks |54| Part 7 | Metrics and Analytics |55| Part 8 | Cross-References |5657---5859## See also6061- [`../../references/math-product-management-handbook.md`](../../references/math-product-management-handbook.md) — Full handbook (extracted from this skill)62- [`../math-project-management/SKILL.md`](../math-project-management/SKILL.md) — Successor63- [`../lean-retro-methodology/SKILL.md`](../lean-retro-methodology/SKILL.md) — Successor64- [`../lean-zettelkasten/SKILL.md`](../lean-zettelkasten/SKILL.md) — Successor65
r-irbe