agentleFS
r-irber-irbe/proof-skills/skills/math-product-management/SKILL.md

math-product-management

Skill3 starsChanged 25 days agoApache-2.0View on GitHub

USE FOR: Product management for mathematical formalization projects: roadmap creation, stakeholder management. DO NOT USE FOR: project-level scheduling (@math-project-management). TRIGGERS: product management, roadmap, stakeholder management.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    STOP if the question is operational scheduling — delegate to @math-project-management.

    line 51
  2. Very specific:

    STOP if a strategic-analysis lens dominates — delegate to @lean-applied-reasoning.

    line 52
  3. Distinctive:

    STOP if data inputs are missing — escalate to audit / blueprint skills first.

    line 53

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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 @lean-applied-reasoning); engineering discipline view (use @applied-engineering-disciplines).
  • TRIGGERS: product management, roadmap, stakeholder management, feature prioritization, formal verification PM.

Workflow

  1. Frame the product question: roadmap, prioritisation, stakeholder communication, or scope decision.
  2. Pick the matching template; identify data inputs needed (theorem counts, dependency graph, coverage matrix).
  3. Produce the artifact (roadmap, RICE table, stakeholder brief).
  4. 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 @lean-applied-reasoning.
  • 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.

SectionTopic
Part 1Product vs. Project Management
Part 2Theorem Portfolio Management
Part 3Stakeholder Analysis
Part 4Roadmap Planning
Part 5Value Analysis
Part 6Decision Frameworks
Part 7Metrics and Analytics
Part 8Cross-References

See also

  • ../../references/math-product-management-handbook.md — Full handbook (extracted from this skill)
  • ../math-project-management/SKILL.md — Successor
  • ../lean-retro-methodology/SKILL.md — Successor
  • ../lean-zettelkasten/SKILL.md — Successor

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.