{
  "schema": 1,
  "generated_by": "scripts/gen-skill-manifest.mjs",
  "catalog": {
    "skills": 68,
    "phase": 30,
    "foundation": 11,
    "utility": 12,
    "tool": 15,
    "sub_agents": 6,
    "commands": 11,
    "workflows": 12
  },
  "entries": [
    {
      "name": "define-hypothesis",
      "description": "Defines a testable hypothesis with clear success metrics and a validation approach. Use when forming assumptions to test or aligning a team on what success looks like, before any experiment is designed. To design the A/B test or experiment that will validate the hypothesis, use measure-experiment-design.",
      "version": "2.1.0",
      "group": "phase",
      "phase": "define",
      "family": null,
      "move": null,
      "path": "skills/define-hypothesis",
      "references": [
        "TEMPLATE.md",
        "EXAMPLE.md"
      ],
      "sample": "library/skill-output-samples/define-hypothesis"
    },
    {
      "name": "define-jtbd-canvas",
      "description": "Creates a Jobs to be Done canvas capturing the functional, emotional, and social dimensions of a customer job. Use when deeply understanding customer motivations, designing for jobs, or reframing product positioning.",
      "version": "2.1.0",
      "group": "phase",
      "phase": "define",
      "family": null,
      "move": null,
      "path": "skills/define-jtbd-canvas",
      "references": [
        "TEMPLATE.md",
        "EXAMPLE.md"
      ],
      "sample": "library/skill-output-samples/define-jtbd-canvas"
    },
    {
      "name": "define-opportunity-tree",
      "description": "Creates an opportunity solution tree mapping desired outcomes to opportunities and potential solutions. Use for outcome-driven product discovery, prioritization, or communicating product strategy.",
      "version": "2.1.0",
      "group": "phase",
      "phase": "define",
      "family": null,
      "move": null,
      "path": "skills/define-opportunity-tree",
      "references": [
        "TEMPLATE.md",
        "EXAMPLE.md"
      ],
      "sample": "library/skill-output-samples/define-opportunity-tree"
    },
    {
      "name": "define-prioritization-framework",
      "description": "Run applicable prioritization frameworks (RICE, ICE, MoSCoW, Weighted Scoring, Kano) against a list of features or initiatives. Produces a comparison table showing where rankings agree and diverge across frameworks, and an executive summary with recommendation. Framework applicability is filtered by data availability; Kano requires customer research. Refuses to fabricate scores; produces an estimation scaffold when input data is missing.",
      "version": "1.0.0",
      "group": "phase",
      "phase": "define",
      "family": null,
      "move": null,
      "path": "skills/define-prioritization-framework",
      "references": [
        "TEMPLATE.md",
        "EXAMPLE.md"
      ],
      "sample": "library/skill-output-samples/define-prioritization-framework"
    },
    {
      "name": "define-problem-statement",
      "description": "Creates a clear problem framing document with user impact, business context, and success criteria. Use when starting a new initiative, realigning a drifted project, or communicating up to leadership.",
      "version": "2.1.0",
      "group": "phase",
      "phase": "define",
      "family": null,
      "move": null,
      "path": "skills/define-problem-statement",
      "references": [
        "TEMPLATE.md",
        "EXAMPLE.md"
      ],
      "sample": "library/skill-output-samples/define-problem-statement"
    },
    {
      "name": "deliver-acceptance-criteria",
      "description": "Generates structured Given/When/Then acceptance criteria for a user story or feature slice, covering the happy path, key failure scenarios, and non-functional expectations in testable form. Use when turning requirements into verifiable scenarios for engineering handoff and QA sign-off. For a dedicated catalog of boundary conditions, error states, and recovery paths across a feature, use deliver-edge-cases; to write the stories themselves, use deliver-user-stories.",
      "version": "1.1.0",
      "group": "phase",
      "phase": "deliver",
      "family": null,
      "move": null,
      "path": "skills/deliver-acceptance-criteria",
      "references": [
        "TEMPLATE.md",
        "EXAMPLE.md"
      ],
      "sample": "library/skill-output-samples/deliver-acceptance-criteria"
    },
    {
      "name": "deliver-edge-cases",
      "description": "Documents edge cases, error states, boundary conditions, race conditions, and recovery paths for a feature - the systematic catalog of what can go wrong and the failure modes to design for. Use during specification to map the failure surface and ensure comprehensive coverage, or during QA planning to identify boundary and limit scenarios to test. Distinct from deliver-acceptance-criteria, which writes story-level Given/When/Then checks; this skill produces the whole-feature edge-case catalog.",
      "version": "2.1.1",
      "group": "phase",
      "phase": "deliver",
      "family": null,
      "move": null,
      "path": "skills/deliver-edge-cases",
      "references": [
        "TEMPLATE.md",
        "EXAMPLE.md"
      ],
      "sample": "library/skill-output-samples/deliver-edge-cases"
    },
    {
      "name": "deliver-launch-checklist",
      "description": "Creates a comprehensive pre-launch checklist covering engineering, design, marketing, support, legal, and operations readiness. Use before releasing features, products, or major updates to ensure nothing is missed.",
      "version": "2.1.0",
      "group": "phase",
      "phase": "deliver",
      "family": null,
      "move": null,
      "path": "skills/deliver-launch-checklist",
      "references": [
        "TEMPLATE.md",
        "EXAMPLE.md"
      ],
      "sample": "library/skill-output-samples/deliver-launch-checklist"
    },
    {
      "name": "deliver-prd",
      "description": "Creates a comprehensive Product Requirements Document that aligns stakeholders on what to build, why, and how success will be measured. Use when specifying features, epics, or product initiatives for engineering handoff.",
      "version": "2.1.0",
      "group": "phase",
      "phase": "deliver",
      "family": null,
      "move": null,
      "path": "skills/deliver-prd",
      "references": [
        "TEMPLATE.md",
        "EXAMPLE.md"
      ],
      "sample": "library/skill-output-samples/deliver-prd"
    },
    {
      "name": "deliver-release-notes",
      "description": "Creates user-facing release notes that communicate new features, improvements, and fixes in clear, benefit-focused language. Use when shipping updates to communicate changes to users, customers, or stakeholders.",
      "version": "2.1.0",
      "group": "phase",
      "phase": "deliver",
      "family": null,
      "move": null,
      "path": "skills/deliver-release-notes",
      "references": [
        "TEMPLATE.md",
        "EXAMPLE.md"
      ],
      "sample": "library/skill-output-samples/deliver-release-notes"
    },
    {
      "name": "deliver-user-stories",
      "description": "Generates user stories in the standard persona, action, benefit story format from product requirements or feature descriptions. Use when breaking a feature into stories for sprint planning, writing tickets, or communicating scope to engineering. For testable Given/When/Then acceptance criteria on a story, use deliver-acceptance-criteria; for boundary and failure scenarios, use deliver-edge-cases.",
      "version": "2.1.0",
      "group": "phase",
      "phase": "deliver",
      "family": null,
      "move": null,
      "path": "skills/deliver-user-stories",
      "references": [
        "TEMPLATE.md",
        "EXAMPLE.md"
      ],
      "sample": "library/skill-output-samples/deliver-user-stories"
    },
    {
      "name": "develop-adr",
      "description": "Creates an Architecture Decision Record following the Nygard format to document significant technical decisions, their context, and consequences. Use when making technical choices that affect system architecture, technology selection, or development patterns.",
      "version": "2.1.0",
      "group": "phase",
      "phase": "develop",
      "family": null,
      "move": null,
      "path": "skills/develop-adr",
      "references": [
        "TEMPLATE.md",
        "EXAMPLE.md"
      ],
      "sample": "library/skill-output-samples/develop-adr"
    },
    {
      "name": "develop-design-rationale",
      "description": "Documents the reasoning behind design decisions including alternatives considered, trade-offs evaluated, and principles applied. Use when making significant UX decisions, aligning with stakeholders on design direction, or preserving design context for future reference.",
      "version": "2.1.0",
      "group": "phase",
      "phase": "develop",
      "family": null,
      "move": null,
      "path": "skills/develop-design-rationale",
      "references": [
        "TEMPLATE.md",
        "EXAMPLE.md"
      ],
      "sample": "library/skill-output-samples/develop-design-rationale"
    },
    {
      "name": "develop-solution-brief",
      "description": "Creates a concise one-page solution overview that communicates the proposed approach, key decisions, and trade-offs. Use when pitching solutions to stakeholders, aligning teams on approach, or documenting solution intent before detailed specification.",
      "version": "2.1.0",
      "group": "phase",
      "phase": "develop",
      "family": null,
      "move": null,
      "path": "skills/develop-solution-brief",
      "references": [
        "TEMPLATE.md",
        "EXAMPLE.md"
      ],
      "sample": "library/skill-output-samples/develop-solution-brief"
    },
    {
      "name": "develop-spike-summary",
      "description": "Documents the results of a time-boxed technical or design exploration (spike). Use after completing a spike to capture learnings, findings, and recommendations for the team.",
      "version": "2.1.0",
      "group": "phase",
      "phase": "develop",
      "family": null,
      "move": null,
      "path": "skills/develop-spike-summary",
      "references": [
        "TEMPLATE.md",
        "EXAMPLE.md"
      ],
      "sample": "library/skill-output-samples/develop-spike-summary"
    },
    {
      "name": "discover-competitive-analysis",
      "description": "Creates a structured competitive analysis comparing features, positioning, and strategy across competitors. Use when entering a market, planning differentiation, or understanding the competitive landscape.",
      "version": "2.1.0",
      "group": "phase",
      "phase": "discover",
      "family": null,
      "move": null,
      "path": "skills/discover-competitive-analysis",
      "references": [
        "TEMPLATE.md",
        "EXAMPLE.md"
      ],
      "sample": "library/skill-output-samples/discover-competitive-analysis"
    },
    {
      "name": "discover-interview-synthesis",
      "description": "Synthesizes user research interviews into actionable insights, patterns, and recommendations. Use after conducting user interviews, customer calls, or usability sessions to extract and communicate findings across participants. Distinct from foundation-meeting-recap, which summarizes one internal meeting for its attendees; this skill aggregates research conversations into evidence-backed findings.",
      "version": "2.1.0",
      "group": "phase",
      "phase": "discover",
      "family": null,
      "move": null,
      "path": "skills/discover-interview-synthesis",
      "references": [
        "TEMPLATE.md",
        "EXAMPLE.md"
      ],
      "sample": "library/skill-output-samples/discover-interview-synthesis"
    },
    {
      "name": "discover-journey-map",
      "description": "Produce a customer journey map covering stages, touchpoints, emotional curve, pain points, moments of truth, and opportunity annotations. Output is a markdown artifact that may include mermaid timeline / flowchart visualization. Supports both linear journey (start to end) and cyclical journey (recurring engagement loops). Refuses to fabricate emotional or behavioral data without research input.",
      "version": "1.0.0",
      "group": "phase",
      "phase": "discover",
      "family": null,
      "move": null,
      "path": "skills/discover-journey-map",
      "references": [
        "TEMPLATE.md",
        "EXAMPLE.md"
      ],
      "sample": "library/skill-output-samples/discover-journey-map"
    },
    {
      "name": "discover-market-sizing",
      "description": "Estimate market opportunity (TAM, SAM, SOM) using multiple sizing frameworks (top-down, bottom-up, comparable company, analogous market). Triangulates across frameworks, highlights where they converge and diverge as signal, and produces a calibrated range with source-graded confidence labels. Refuses unbounded fabrications; always offers a labeled lower-confidence path when data is thin. Used for investment cases, go/no-go decisions, and stakeholder pitches.",
      "version": "1.0.0",
      "group": "phase",
      "phase": "discover",
      "family": null,
      "move": null,
      "path": "skills/discover-market-sizing",
      "references": [
        "TEMPLATE.md",
        "EXAMPLE.md"
      ],
      "sample": "library/skill-output-samples/discover-market-sizing"
    },
    {
      "name": "discover-stakeholder-summary",
      "description": "Documents stakeholder needs, concerns, and influence for a project or initiative. Use when starting projects, managing complex stakeholder relationships, or ensuring alignment across organizational boundaries.",
      "version": "2.1.0",
      "group": "phase",
      "phase": "discover",
      "family": null,
      "move": null,
      "path": "skills/discover-stakeholder-summary",
      "references": [
        "TEMPLATE.md",
        "EXAMPLE.md"
      ],
      "sample": "library/skill-output-samples/discover-stakeholder-summary"
    },
    {
      "name": "foundation-build-risk-review",
      "description": "Runs a fast pre-build risk review on a product idea, feature request, or scope change, naming the single assumption most likely to make it fail and returning a clear verdict (build small, validate first, pivot first, or don't build yet) with a no-code validation step. Use before committing build effort, when triaging whether to honor a feature request, or when deciding whether to expand scope, ahead of writing a PRD. For a launched product's pivot-or-persevere decision, use iterate-pivot-decision instead.",
      "version": "1.0.0",
      "group": "foundation",
      "phase": null,
      "family": null,
      "move": null,
      "path": "skills/foundation-build-risk-review",
      "references": [
        "TEMPLATE.md",
        "EXAMPLE.md"
      ],
      "sample": "library/skill-output-samples/foundation-build-risk-review"
    },
    {
      "name": "foundation-lean-canvas",
      "description": "Produces a one-page lean canvas across nine interlocking blocks (problem, customer, UVP, solution, channels, revenue, cost, metrics, unfair advantage) with optional inline HTML and SVG visual rendering. Use when framing a new product thesis, stress-testing an existing strategy, comparing strategic options side-by-side, or aligning a team on business-model assumptions. Works as a strategic hub that cross-links to deeper PM skills without duplicating them.",
      "version": "1.0.0",
      "group": "foundation",
      "phase": null,
      "family": null,
      "move": null,
      "path": "skills/foundation-lean-canvas",
      "references": [
        "TEMPLATE.md",
        "EXAMPLE.md"
      ],
      "sample": "library/skill-output-samples/foundation-lean-canvas"
    },
    {
      "name": "foundation-meeting-agenda",
      "description": "Produces an attendee-facing agenda that sets what will be discussed, who owns each topic, and how time will be spent. Supports ten meeting type variants (standup, planning, review, decision-making, brainstorm, 1-on-1, stakeholder-review, project-kickoff, working-session, exec-briefing). Emits a shareable summary suitable for Slack or email plus a full agenda with time-boxed topics, type tags, owners, attendee prep, and logistics.",
      "version": "1.0.0",
      "group": "foundation",
      "phase": null,
      "family": null,
      "move": null,
      "path": "skills/foundation-meeting-agenda",
      "references": [
        "TEMPLATE.md",
        "EXAMPLE.md"
      ],
      "sample": "library/skill-output-samples/foundation-meeting-agenda"
    },
    {
      "name": "foundation-meeting-brief",
      "description": "Produces a private strategic preparation document for the user before a meeting that matters. Captures stakes, stakeholder positions and reads, ranked desired outcomes, key messages, anticipated questions with prepared responses, risks and tensions, specific asks, and success signals. Distinct from meeting-agenda because this artifact is not shared with attendees; it is the user's personal tactical prep for meetings where positioning matters.",
      "version": "1.0.0",
      "group": "foundation",
      "phase": null,
      "family": null,
      "move": null,
      "path": "skills/foundation-meeting-brief",
      "references": [
        "TEMPLATE.md",
        "EXAMPLE.md"
      ],
      "sample": "library/skill-output-samples/foundation-meeting-brief"
    },
    {
      "name": "foundation-meeting-recap",
      "description": "Produces a topic-segmented post-meeting summary for attendees with decisions highlighted and actions captured inline per topic (plus a consolidated action view at the end). Auto-populates topic skeleton from a sibling meeting-agenda when available and reconciles planned vs. actual topics. Accepts transcripts from Zoom, Meet, Otter, Fireflies, Krisp MCP, or manual notes; runs on variable-quality input without blocking. For synthesizing user research interviews across participants, use discover-interview-synthesis.",
      "version": "1.0.2",
      "group": "foundation",
      "phase": null,
      "family": null,
      "move": null,
      "path": "skills/foundation-meeting-recap",
      "references": [
        "TEMPLATE.md",
        "EXAMPLE.md"
      ],
      "sample": "library/skill-output-samples/foundation-meeting-recap"
    },
    {
      "name": "foundation-meeting-synthesize",
      "description": "Cross-meeting archaeology skill. Consumes multiple meeting recaps (or raw notes) over a period and surfaces patterns invisible in any single meeting. Shows how decisions evolved, who has been saying what, where threads are stalling, and where contradictions have emerged. Produces a plain-text timeline, themes with confidence markers, stakeholder position tracking, consolidated decision list, contradiction flags, open items, narrative summary, and prioritized follow-ups.",
      "version": "1.0.1",
      "group": "foundation",
      "phase": null,
      "family": null,
      "move": null,
      "path": "skills/foundation-meeting-synthesize",
      "references": [
        "TEMPLATE.md",
        "EXAMPLE.md"
      ],
      "sample": "library/skill-output-samples/foundation-meeting-synthesize"
    },
    {
      "name": "foundation-okr-writer",
      "description": "Drafts, reviews, rewrites, and coaches outcome-based OKR sets across team, department, product, or company scopes. Supports five entry modes (Guided default, One-Shot via --oneshot, Sustained Coach, Audit Only, Rewrite). Diagnoses empowered-team context and adjusts framing; refuses to fabricate baselines or targets; refuses to use OKR scores for compensation; reframes feature-delivery KRs into outcome KRs. Use when planning quarterly OKRs, translating strategy into team outcomes, reviewing draft OKRs for quality, or converting roadmap-as-OKR drafts into proper OKR sets.",
      "version": "1.0.0",
      "group": "foundation",
      "phase": null,
      "family": null,
      "move": null,
      "path": "skills/foundation-okr-writer",
      "references": [
        "TEMPLATE.md",
        "EXAMPLE.md"
      ],
      "sample": "library/skill-output-samples/foundation-okr-writer"
    },
    {
      "name": "foundation-persona",
      "description": "Generates an evidence-calibrated product or marketing persona using the canonical v2.5 output contract. Use when shaping artifact perspective, stress-testing decisions, or framing product and GTM strategy.",
      "version": "2.6.0",
      "group": "foundation",
      "phase": null,
      "family": null,
      "move": null,
      "path": "skills/foundation-persona",
      "references": [
        "TEMPLATE.md",
        "EXAMPLE.md"
      ],
      "sample": "library/skill-output-samples/foundation-persona"
    },
    {
      "name": "foundation-prioritized-action-plan",
      "description": "Produce a comprehensive, evidence-grounded prioritized action plan from any PM input (notes, transcripts, drafts, executive asks, Slack threads, or a raw situation). Outputs one saveable document with an executive summary, input mirror, situation classification (Cynefin), the binding constraint (Theory of Constraints), prioritized questions and open decisions, a ranked action plan with the critical effort plus follow-ons, risks and pre-mortem, copy/paste prompts for downstream pm-skills, and an evidence map. Builds a source ledger and cites exact input quotes; refuses High-confidence plans for Complex or Chaotic situations. Use when you want the critical next effort and how to execute it.",
      "version": "1.1.0",
      "group": "foundation",
      "phase": null,
      "family": null,
      "move": null,
      "path": "skills/foundation-prioritized-action-plan",
      "references": [
        "TEMPLATE.md",
        "EXAMPLE.md"
      ],
      "sample": "library/skill-output-samples/foundation-prioritized-action-plan"
    },
    {
      "name": "foundation-stakeholder-briefings",
      "description": "Turns any source artifact (spec, discovery, research, GTM plan, experiment results, retro, or raw notes) into one canonical master document plus a set of audience-tailored briefings, each re-pitched to a stakeholder lens (executive, board, engineering, UX, PMM, sales, CS, legal, data, or a custom audience). Every briefing is a traceable projection of the master, so the versions never disagree. Use when one piece of work must reach several audiences who each need a different framing, decision, and level of detail.",
      "version": "1.0.0",
      "group": "foundation",
      "phase": null,
      "family": null,
      "move": null,
      "path": "skills/foundation-stakeholder-briefings",
      "references": [
        "TEMPLATE.md",
        "EXAMPLE.md"
      ],
      "sample": "library/skill-output-samples/foundation-stakeholder-briefings"
    },
    {
      "name": "foundation-stakeholder-update",
      "description": "Produces async communication to stakeholders, primarily non-attendees and secondarily some attendees who want a reference. Translates meeting outcomes into what-it-means language for readers, with channel variants (slack, teams, email, notion, exec-memo) and audience variants (engineering, design, leadership, customer-facing, mixed). Surfaces a primary CTA up front, flags technical-to-business translations for user verification, and detects thread continuation from prior updates.",
      "version": "1.0.0",
      "group": "foundation",
      "phase": null,
      "family": null,
      "move": null,
      "path": "skills/foundation-stakeholder-update",
      "references": [
        "TEMPLATE.md",
        "EXAMPLE.md"
      ],
      "sample": "library/skill-output-samples/foundation-stakeholder-update"
    },
    {
      "name": "iterate-lessons-log",
      "description": "Creates a structured lessons learned entry for organizational memory. Use after an incident, a completed project, or a significant learning to record knowledge for future teams and initiatives. Distinct from iterate-retrospective, which facilitates the team ceremony; this skill writes the durable lessons entry that outlives it.",
      "version": "2.1.0",
      "group": "phase",
      "phase": "iterate",
      "family": null,
      "move": null,
      "path": "skills/iterate-lessons-log",
      "references": [
        "TEMPLATE.md",
        "EXAMPLE.md"
      ],
      "sample": "library/skill-output-samples/iterate-lessons-log"
    },
    {
      "name": "iterate-pivot-decision",
      "description": "Documents a strategic pivot or persevere decision with the evidence, analysis, and rationale. Use when evaluating whether to change direction on a product, feature, or strategy based on market feedback.",
      "version": "2.1.1",
      "group": "phase",
      "phase": "iterate",
      "family": null,
      "move": null,
      "path": "skills/iterate-pivot-decision",
      "references": [
        "TEMPLATE.md",
        "EXAMPLE.md"
      ],
      "sample": "library/skill-output-samples/iterate-pivot-decision"
    },
    {
      "name": "iterate-refinement-notes",
      "description": "Documents backlog refinement session outcomes including stories refined, estimates, questions raised, and decisions made. Use during or after refinement to capture the results and share with absent team members.",
      "version": "2.1.0",
      "group": "phase",
      "phase": "iterate",
      "family": null,
      "move": null,
      "path": "skills/iterate-refinement-notes",
      "references": [
        "TEMPLATE.md",
        "EXAMPLE.md"
      ],
      "sample": "library/skill-output-samples/iterate-refinement-notes"
    },
    {
      "name": "iterate-retrospective",
      "description": "Facilitates and documents a team retrospective capturing what went well, what to improve, and action items. Use at the end of a sprint, project, or milestone to reflect and improve team practices. To bank individual learnings into organizational memory afterward, use iterate-lessons-log.",
      "version": "2.1.0",
      "group": "phase",
      "phase": "iterate",
      "family": null,
      "move": null,
      "path": "skills/iterate-retrospective",
      "references": [
        "TEMPLATE.md",
        "EXAMPLE.md"
      ],
      "sample": "library/skill-output-samples/iterate-retrospective"
    },
    {
      "name": "measure-dashboard-requirements",
      "description": "Specifies requirements for an analytics dashboard including metrics, visualizations, filters, and data sources. Use when requesting dashboards from data teams, defining KPI tracking, or documenting reporting needs.",
      "version": "2.1.0",
      "group": "phase",
      "phase": "measure",
      "family": null,
      "move": null,
      "path": "skills/measure-dashboard-requirements",
      "references": [
        "TEMPLATE.md",
        "EXAMPLE.md"
      ],
      "sample": "library/skill-output-samples/measure-dashboard-requirements"
    },
    {
      "name": "measure-experiment-design",
      "description": "Designs an A/B test or experiment with variants, success metrics, sample size, and duration for an existing hypothesis. Use when planning an experiment to validate a product change or test an assumption you have already framed. To articulate the hypothesis itself first, use define-hypothesis.",
      "version": "2.1.0",
      "group": "phase",
      "phase": "measure",
      "family": null,
      "move": null,
      "path": "skills/measure-experiment-design",
      "references": [
        "TEMPLATE.md",
        "EXAMPLE.md"
      ],
      "sample": "library/skill-output-samples/measure-experiment-design"
    },
    {
      "name": "measure-experiment-results",
      "description": "Documents the results of a completed experiment or A/B test with statistical analysis, learnings, and recommendations. Use after experiments conclude to communicate findings, inform decisions, and build organizational knowledge.",
      "version": "2.1.0",
      "group": "phase",
      "phase": "measure",
      "family": null,
      "move": null,
      "path": "skills/measure-experiment-results",
      "references": [
        "TEMPLATE.md",
        "EXAMPLE.md"
      ],
      "sample": "library/skill-output-samples/measure-experiment-results"
    },
    {
      "name": "measure-instrumentation-spec",
      "description": "Specifies event tracking and analytics instrumentation requirements for a feature. Use when defining what data to collect, ensuring consistent tracking implementation, or documenting analytics requirements for engineering.",
      "version": "2.1.0",
      "group": "phase",
      "phase": "measure",
      "family": null,
      "move": null,
      "path": "skills/measure-instrumentation-spec",
      "references": [
        "TEMPLATE.md",
        "EXAMPLE.md"
      ],
      "sample": "library/skill-output-samples/measure-instrumentation-spec"
    },
    {
      "name": "measure-okr-grader",
      "description": "Scores completed OKR sets at cycle close with KR-level scoring per the canonical OKR type enum (committed | aspirational | learning | operational_health | compliance_or_safety), committed-vs-aspirational interpretation, evidence quality assessment, learning synthesis, and next-cycle recommendations. Refuses to retroactively change targets or shrink committed scope, average away guardrail KRs, treat 0.7 as success for committed or compliance_or_safety KRs, equate effort with impact, or use scores for individual performance. Hands off to iterate-lessons-log, iterate-retrospective, define-hypothesis, measure-dashboard-requirements, measure-instrumentation-spec, and foundation-okr-writer.",
      "version": "1.0.0",
      "group": "phase",
      "phase": "measure",
      "family": null,
      "move": null,
      "path": "skills/measure-okr-grader",
      "references": [
        "TEMPLATE.md",
        "EXAMPLE.md"
      ],
      "sample": "library/skill-output-samples/measure-okr-grader"
    },
    {
      "name": "measure-survey-analysis",
      "description": "Analyze survey results into actionable PM insights. Produces persona segmentation, hypothesis validation status, thematic clustering of open-text responses, statistical confidence labels, prioritized recommendations, and what-NOT-to-conclude warnings. Refuses to overstate statistical significance from weak samples or biased instruments.",
      "version": "1.0.0",
      "group": "phase",
      "phase": "measure",
      "family": null,
      "move": null,
      "path": "skills/measure-survey-analysis",
      "references": [
        "TEMPLATE.md",
        "EXAMPLE.md"
      ],
      "sample": "library/skill-output-samples/measure-survey-analysis"
    },
    {
      "name": "tool-design-sprint-brief",
      "description": "Pre-sprint brief that locks challenge, sprint questions, team and role assignments, customer recruiting plan, prototype medium, interview format, logistics, and success criteria before Monday of a Design Sprint. Use after the readiness verdict is Go and before Monday begins. Produces a two-page artifact the team and Decider sign off on as the contract for the next five days.",
      "version": "0.1.0",
      "group": "tool",
      "phase": null,
      "family": "design-sprint",
      "move": "brief",
      "path": "skills/tool-design-sprint-brief",
      "references": [
        "TEMPLATE.md",
        "EXAMPLE.md"
      ],
      "sample": "library/skill-output-samples/tool-design-sprint-brief"
    },
    {
      "name": "tool-design-sprint-decide-and-storyboard",
      "description": "Day 3 (Wednesday) move of a Design Sprint that runs the art museum layout, heat map, speed critique, straw poll, Decider supervote, rumble-vs-all-in-one decision, and the storyboard that drives Thursday's prototype build. The most decision-heavy day of the sprint. Use Wednesday morning and afternoon after Tuesday's sketches are collected and attribution-stripped. Produces the canonical 5-15 step storyboard that becomes the build spec.",
      "version": "0.1.0",
      "group": "tool",
      "phase": null,
      "family": "design-sprint",
      "move": "decide-and-storyboard",
      "path": "skills/tool-design-sprint-decide-and-storyboard",
      "references": [
        "TEMPLATE.md",
        "EXAMPLE.md"
      ],
      "sample": "library/skill-output-samples/tool-design-sprint-decide-and-storyboard"
    },
    {
      "name": "tool-design-sprint-map-and-target",
      "description": "Day 1 (Monday) move of a Design Sprint that produces the bundled Monday artifact containing long-term goal, sprint questions (3-7 testable risks), customer or system map (5-15 step flow), expert interview notes, HMW (How Might We) cluster board, and the Decider's chosen target moment. Use Day 1 morning and afternoon after the sprint brief is locked. Sets the design target for Tuesday's sketches and Wednesday's storyboard.",
      "version": "0.1.0",
      "group": "tool",
      "phase": null,
      "family": "design-sprint",
      "move": "map-and-target",
      "path": "skills/tool-design-sprint-map-and-target",
      "references": [
        "TEMPLATE.md",
        "EXAMPLE.md"
      ],
      "sample": "library/skill-output-samples/tool-design-sprint-map-and-target"
    },
    {
      "name": "tool-design-sprint-prototype-plan",
      "description": "Day 4 (Thursday) move of a Design Sprint that produces the planning artifact for the day. Output covers the prototype role plan (Maker, Stitcher, Writer, Asset Collector, Interviewer), prototype brief (what to build, fidelity bar, time allocation per role), canonical Five-Act Interview script (Welcome, Context, Intro, Tasks, Debrief), trial-run checklist, and Friday participant confirmation tracker. The actual prototype build is craft work outside the skill's AI invocation surface. Use Thursday morning after Wednesday's storyboard is signed off.",
      "version": "0.1.0",
      "group": "tool",
      "phase": null,
      "family": "design-sprint",
      "move": "prototype-plan",
      "path": "skills/tool-design-sprint-prototype-plan",
      "references": [
        "TEMPLATE.md",
        "EXAMPLE.md"
      ],
      "sample": "library/skill-output-samples/tool-design-sprint-prototype-plan"
    },
    {
      "name": "tool-design-sprint-readiness",
      "description": "Pre-sprint diagnostic that determines whether a team should run a Design Sprint now, postpone it, or do prerequisite work first. Produces a Go / Conditional Go / Wait verdict with diagnosis, recommended preconditions, attendee list, customer recruiting plan, and pre-sprint activities. Use when a team is considering starting a Design Sprint and wants a fast yes/no diagnosis before committing five days of team time and customer recruiting cost.",
      "version": "0.1.0",
      "group": "tool",
      "phase": null,
      "family": "design-sprint",
      "move": "readiness",
      "path": "skills/tool-design-sprint-readiness",
      "references": [
        "TEMPLATE.md",
        "EXAMPLE.md"
      ],
      "sample": "library/skill-output-samples/tool-design-sprint-readiness"
    },
    {
      "name": "tool-design-sprint-sketch",
      "description": "Day 2 (Tuesday) move of a Design Sprint that structures lightning demos and the four-step independent solution sketch protocol (Notes, Ideas, Crazy 8s, Solution Sketch). Each team member produces one solution sketch individually; the skill orchestrates the day but does not author the sketches themselves. Use Tuesday morning after Monday's target moment is locked. Output is the lightning demo board, sketch assignments, and the cohort of independent sketches that become Wednesday's heat-map material.",
      "version": "0.1.0",
      "group": "tool",
      "phase": null,
      "family": "design-sprint",
      "move": "sketch",
      "path": "skills/tool-design-sprint-sketch",
      "references": [
        "TEMPLATE.md",
        "EXAMPLE.md"
      ],
      "sample": "library/skill-output-samples/tool-design-sprint-sketch"
    },
    {
      "name": "tool-design-sprint-test-and-score",
      "description": "Day 5 (Friday) sprint-closing move of a Design Sprint that produces the bundled Friday artifact covering per-customer interview observations, best quotes, scorecard grid (sprint questions by customers), observed patterns, hot takes from each team member, and the Decider summary (build, iterate, pivot, or stop, plus highest-confidence learning, most important revision, and next artifact). Use Friday after Thursday's prototype passes trial run and during/after the 5 customer interviews. The sprint's payoff artifact.",
      "version": "0.1.0",
      "group": "tool",
      "phase": null,
      "family": "design-sprint",
      "move": "test-and-score",
      "path": "skills/tool-design-sprint-test-and-score",
      "references": [
        "TEMPLATE.md",
        "EXAMPLE.md"
      ],
      "sample": "library/skill-output-samples/tool-design-sprint-test-and-score"
    },
    {
      "name": "tool-foundation-sprint-approach-options",
      "description": "Day 2 morning move of a Foundation Sprint. Forces generation of 3 to 7 candidate approaches as one-page summaries before the team converges on a top bet. Use after Day 1 is signed and before Magic Lenses on Day 2 afternoon. Enforces a minimum of 3 approaches to prevent first-idea anchoring. Each approach summary names what it is, why it serves the differentiators, and includes a simple visual.",
      "version": "0.1.0",
      "group": "tool",
      "phase": null,
      "family": "foundation-sprint",
      "move": "approach-options",
      "path": "skills/tool-foundation-sprint-approach-options",
      "references": [
        "TEMPLATE.md",
        "EXAMPLE.md"
      ],
      "sample": "library/skill-output-samples/tool-foundation-sprint-approach-options"
    },
    {
      "name": "tool-foundation-sprint-basics",
      "description": "Day 1 morning move of a Foundation Sprint. Forces explicit team choices on target customer, important problem, team advantage, and competitors and alternatives. Produces a single coherent strategic frame that becomes the input to Day 1 afternoon Differentiation. Use after the sprint brief is signed and Day 1 morning is scheduled. Bundled artifact, not four separate decisions.",
      "version": "0.1.0",
      "group": "tool",
      "phase": null,
      "family": "foundation-sprint",
      "move": "basics",
      "path": "skills/tool-foundation-sprint-basics",
      "references": [
        "TEMPLATE.md",
        "EXAMPLE.md"
      ],
      "sample": "library/skill-output-samples/tool-foundation-sprint-basics"
    },
    {
      "name": "tool-foundation-sprint-brief",
      "description": "Pre-sprint brief that locks scope, the decision the sprint must unlock, team and role assignments, logistics, inputs to bring, and success criteria before Day 1 of a Foundation Sprint. Use after the readiness verdict is Go and before the sprint begins. Produces a one-page artifact the team and Decider sign off on as the contract for the next two days.",
      "version": "0.1.0",
      "group": "tool",
      "phase": null,
      "family": "foundation-sprint",
      "move": "brief",
      "path": "skills/tool-foundation-sprint-brief",
      "references": [
        "TEMPLATE.md",
        "EXAMPLE.md"
      ],
      "sample": "library/skill-output-samples/tool-foundation-sprint-brief"
    },
    {
      "name": "tool-foundation-sprint-differentiation",
      "description": "Day 1 afternoon move of a Foundation Sprint. Converts the morning's Basics frame into a defensible strategic position by scoring differentiator candidates against customer-perceived value, choosing two committed differentiators, plotting alternatives on a 2x2 chart, writing decision principles, and producing a one-page Mini Manifesto. Use after Basics is signed; before Approach Options the next morning.",
      "version": "0.1.0",
      "group": "tool",
      "phase": null,
      "family": "foundation-sprint",
      "move": "differentiation",
      "path": "skills/tool-foundation-sprint-differentiation",
      "references": [
        "TEMPLATE.md",
        "EXAMPLE.md"
      ],
      "sample": "library/skill-output-samples/tool-foundation-sprint-differentiation"
    },
    {
      "name": "tool-foundation-sprint-founding-hypothesis",
      "description": "Day 2 end capstone move of a Foundation Sprint. Compresses the sprint's full strategic frame into a single canonical sentence (the Founding Hypothesis) plus an assumption scorecard, why-we-believe, what-could-prove-us-wrong, and recommended next validation step. Use after Magic Lenses is signed. Strict canonical template; paraphrase is not accepted in v0.1.0. The Founding Hypothesis is the spine artifact the sprint exists to produce.",
      "version": "0.1.0",
      "group": "tool",
      "phase": null,
      "family": "foundation-sprint",
      "move": "founding-hypothesis",
      "path": "skills/tool-foundation-sprint-founding-hypothesis",
      "references": [
        "TEMPLATE.md",
        "EXAMPLE.md"
      ],
      "sample": "library/skill-output-samples/tool-foundation-sprint-founding-hypothesis"
    },
    {
      "name": "tool-foundation-sprint-magic-lenses",
      "description": "Day 2 afternoon move of a Foundation Sprint. Evaluates the candidate approach set through multiple lenses (4 classic plus at least 1 custom) to surface trade-offs, identify consistent winners and contradictions, and produce a top bet plus a backup plan. Use after Approach Options is signed. Lens scoring is a sense-making tool, not mathematical truth; arbitrary precision is a smell.",
      "version": "0.1.0",
      "group": "tool",
      "phase": null,
      "family": "foundation-sprint",
      "move": "magic-lenses",
      "path": "skills/tool-foundation-sprint-magic-lenses",
      "references": [
        "TEMPLATE.md",
        "EXAMPLE.md"
      ],
      "sample": "library/skill-output-samples/tool-foundation-sprint-magic-lenses"
    },
    {
      "name": "tool-foundation-sprint-readiness",
      "description": "Pre-sprint diagnostic that determines whether a team should run a Foundation Sprint now, postpone it, or do prerequisite work first. Produces a Go / Conditional Go / Wait verdict with diagnosis, recommended preconditions, attendee list, and pre-sprint activities. Use when a team is considering starting a Foundation Sprint and wants a fast yes/no diagnosis before committing two days of facilitated work.",
      "version": "0.1.0",
      "group": "tool",
      "phase": null,
      "family": "foundation-sprint",
      "move": "readiness",
      "path": "skills/tool-foundation-sprint-readiness",
      "references": [
        "TEMPLATE.md",
        "EXAMPLE.md"
      ],
      "sample": "library/skill-output-samples/tool-foundation-sprint-readiness"
    },
    {
      "name": "tool-note-and-vote",
      "description": "Structured group-decision mechanic that captures silent ideation, voting summaries, and Decider sign-off in a single bundled artifact. Use when a small team needs to make a fast decision with diverse input, when groupthink is a risk, or when a workshop moment demands silent contribution before discussion. Applicable to Foundation Sprint, Design Sprint, and any participatory decision context.",
      "version": "0.1.0",
      "group": "tool",
      "phase": null,
      "family": null,
      "move": null,
      "path": "skills/tool-note-and-vote",
      "references": [
        "TEMPLATE.md",
        "EXAMPLE.md"
      ],
      "sample": "library/skill-output-samples/tool-note-and-vote"
    },
    {
      "name": "utility-mermaid-diagrams",
      "description": "Teaches PMs to create syntactically valid mermaid diagrams by selecting the right diagram type for their communication need, following syntax validity rules, and validating before shipping. Covers all 15 mermaid diagram types with PM-relevant examples and a dual-lens navigation system.",
      "version": "1.0.0",
      "group": "utility",
      "phase": null,
      "family": null,
      "move": null,
      "path": "skills/utility-mermaid-diagrams",
      "references": [
        "TEMPLATE.md",
        "EXAMPLE.md"
      ],
      "sample": "library/skill-output-samples/utility-mermaid-diagrams"
    },
    {
      "name": "utility-pm-changelog-curator",
      "description": "Draft CHANGELOG entries from git log via the pm-changelog-curator sub-agent, applying the repo hygiene rules (describe what changed, public paths only, no attribution trailers). Returns a layered draft with a status summary for maintainer review; refuses a dirty working tree unless --committed-only is passed. Use when banking unreleased changes or preparing a release.",
      "version": "1.0.1",
      "group": "utility",
      "phase": null,
      "family": null,
      "move": null,
      "path": "skills/utility-pm-changelog-curator",
      "references": [
        "TEMPLATE.md",
        "EXAMPLE.md"
      ]
    },
    {
      "name": "utility-pm-critic",
      "description": "Run adversarial review on a PM artifact via the pm-critic sub-agent. Returns findings graded P0/P1/P2/P3 with a concrete fix suggestion per finding and a machine-readable status block. Use after producing a PRD, meeting recap, OKR set, persona, or any PM artifact you want stress-tested before it ships.",
      "version": "1.0.1",
      "group": "utility",
      "phase": null,
      "family": null,
      "move": null,
      "path": "skills/utility-pm-critic",
      "references": [
        "TEMPLATE.md",
        "EXAMPLE.md"
      ]
    },
    {
      "name": "utility-pm-release-conductor",
      "description": "Walk the guided 6-gate release runbook (G0 readiness, G1 adversarial review, G2 version bump and CHANGELOG, G2.5 commit and re-verify, G3 tag and push, G4 post-tag hygiene) via the pm-release-conductor sub-agent. Refuses gate bypasses and tags only the re-verified SHA. Use when cutting a pm-skills release.",
      "version": "1.0.1",
      "group": "utility",
      "phase": null,
      "family": null,
      "move": null,
      "path": "skills/utility-pm-release-conductor",
      "references": [
        "TEMPLATE.md",
        "EXAMPLE.md"
      ]
    },
    {
      "name": "utility-pm-skill-auditor",
      "description": "Run a repo-wide cross-cutting governance audit via the pm-skill-auditor sub-agent. Aggregates the enforcing validator suite, re-derives aggregate counters, and surfaces cross-cutting issues no single validator catches, graded P0/P1/P2/P3 with a machine-readable status. Use for pre-release readiness checks or a periodic repo health audit.",
      "version": "1.0.1",
      "group": "utility",
      "phase": null,
      "family": null,
      "move": null,
      "path": "skills/utility-pm-skill-auditor",
      "references": [
        "TEMPLATE.md",
        "EXAMPLE.md"
      ]
    },
    {
      "name": "utility-pm-skill-builder",
      "description": "Guides contributors from a PM skill idea to a complete Skill Implementation Packet aligned with pm-skills conventions. Runs gap analysis, validates through a Why Gate, classifies by type and phase, generates draft files, and writes to a staging area for review before promotion.",
      "version": "1.1.2",
      "group": "utility",
      "phase": null,
      "family": null,
      "move": null,
      "path": "skills/utility-pm-skill-builder",
      "references": [
        "TEMPLATE.md",
        "EXAMPLE.md"
      ],
      "sample": "library/skill-output-samples/utility-pm-skill-builder"
    },
    {
      "name": "utility-pm-skill-iterate",
      "description": "Applies targeted improvements to an existing pm-skills skill based on feedback, validation reports, or convention changes. Reads current files, previews proposed changes, writes on confirmation, and suggests a version bump. Use when improving a skill after validation or feedback.",
      "version": "1.0.0",
      "group": "utility",
      "phase": null,
      "family": null,
      "move": null,
      "path": "skills/utility-pm-skill-iterate",
      "references": [
        "TEMPLATE.md",
        "EXAMPLE.md"
      ],
      "sample": "library/skill-output-samples/utility-pm-skill-iterate"
    },
    {
      "name": "utility-pm-skill-validate",
      "description": "Audits an existing pm-skills skill against structural conventions and quality criteria. Produces a structured validation report with pass/fail checks, severity-graded findings, and actionable recommendations. Use when checking whether a skill meets repo standards before shipping or after making changes.",
      "version": "1.1.0",
      "group": "utility",
      "phase": null,
      "family": null,
      "move": null,
      "path": "skills/utility-pm-skill-validate",
      "references": [
        "TEMPLATE.md",
        "EXAMPLE.md"
      ],
      "sample": "library/skill-output-samples/utility-pm-skill-validate"
    },
    {
      "name": "utility-pm-workflow-builder",
      "description": "Guides a contributor from a workflow idea to a complete Workflow Implementation Packet (draft workflow file, draft workflow command, cross-cutting update checklist) in a staging area for review. Runs overlap analysis against the existing workflows with a Why Gate, then helps select and sequence skills with authored handoffs. Use when creating a new multi-skill workflow or promoting a repeated ad-hoc chain into a durable one. To build a single skill instead, use utility-pm-skill-builder; to run a sequence without authoring anything, use the chain command or utility-pm-workflow-orchestrator.",
      "version": "1.0.0",
      "group": "utility",
      "phase": null,
      "family": null,
      "move": null,
      "path": "skills/utility-pm-workflow-builder",
      "references": [
        "TEMPLATE.md",
        "EXAMPLE.md"
      ],
      "sample": "library/skill-output-samples/utility-pm-workflow-builder"
    },
    {
      "name": "utility-pm-workflow-orchestrator",
      "description": "Run an ordered sequence of pm-skills against one input, pausing for go/no-go and stopping on a failed or empty step. Accepts a saved prioritized action plan (Mode A) or an ad-hoc named chain (Mode B; the chain command routes here). Explicit invocation only; run --dry-run first while the native path is EXPERIMENTAL. To author a durable workflow instead, use utility-pm-workflow-builder.",
      "version": "1.1.0",
      "group": "utility",
      "phase": null,
      "family": null,
      "move": null,
      "path": "skills/utility-pm-workflow-orchestrator",
      "references": [
        "TEMPLATE.md",
        "EXAMPLE.md"
      ]
    },
    {
      "name": "utility-slideshow-creator",
      "description": "Generates professional presentations from a JSON deck specification using 18 slide types with dark/light variants, content-to-layout decision logic, and calibrated character limits. Ships with a default professional theme.",
      "version": "1.0.1",
      "group": "utility",
      "phase": null,
      "family": null,
      "move": null,
      "path": "skills/utility-slideshow-creator",
      "references": [
        "TEMPLATE.md",
        "EXAMPLE.md"
      ],
      "sample": "library/skill-output-samples/utility-slideshow-creator"
    },
    {
      "name": "utility-update-pm-skills",
      "description": "Checks for newer pm-skills releases, compares local vs. latest version, previews what would change, and updates local files after user confirmation. Generates a structured update report documenting changed files, new capabilities, and the value delta between versions. Use when you want to bring a local pm-skills installation up to date.",
      "version": "1.0.0",
      "group": "utility",
      "phase": null,
      "family": null,
      "move": null,
      "path": "skills/utility-update-pm-skills",
      "references": [
        "TEMPLATE.md",
        "EXAMPLE.md"
      ],
      "sample": "library/skill-output-samples/utility-update-pm-skills"
    }
  ]
}
