MasteryMade · Operations PRD

PRD 12: Batch MANUAL.md Generation

PRD 12 of 12 Depends: PRD 1
Parent: Master Registry v1.0 — Sections 09, 12 · Owner: Lane D (Agent Swarms)

12.1 Purpose

24 active skills, zero MANUAL.md, zero HC pages. High-leverage batch operation: agent swarm reads each SKILL.md → generates MANUAL.md + HC page + registry entry. Once complete, every skill is discoverable, documented, and has a self-healing changelog.

12.2 Agent Swarm Spec

Input per skill

{ "skill_name":"expert-research", "skill_md_path":"/mnt/skills/user/expert-research/SKILL.md",
  "skill_md_content":"...", "registry_section":"6a", "gate_access":[2,3] }

Transformation rules

SKILL.md fieldMANUAL.md fieldTransformation
nameIdentity → nameDirect copy
descriptionIdentity → purposeRewrite: "This service [does X] for [audience] by [method]."
Trigger patternsCapabilities → triggersExtract activation conditions
Core logicCapabilities → what it doesSummarize as input→output pairs
DependenciesDependencies tableIdentify other skills/services called
(not in SKILL.md)Failure modesAI-generated: "Given this logic, what could go wrong?"
(not in SKILL.md)Changelog"Generated from SKILL.md by agent swarm, [date]"

Generation prompt

You are generating a MANUAL.md for "{skill_name}".
SKILL.md content: {content}
Template: {template}

RULES:
- Identity = one sentence, what + why
- Capabilities = specific input→output pairs, not vague descriptions
- "Does NOT do" = at least 2 explicit boundaries
- Failure modes = at least 3 ways this could fail, with recovery
- Changelog starts with "Generated from SKILL.md by agent swarm, {date}"
- Do NOT invent capabilities not in SKILL.md
- If I/O format is vague, note "Format TBD" rather than guessing

12.3 Quality Gate

Automated checks

All required sections present (Identity, Capabilities, Dependencies, Failure Modes, Changelog). Generated capabilities don't contradict SKILL.md. Valid markdown. Input/output schemas are valid JSON Schema or marked TBD.

Human review (sampled)

First 3 generated: full human review (Jason). After 3 approved: spot-check every 5th. If quality degrades: pause, adjust prompt.

12.4 HC Page Generation

  1. Convert markdown to HTML with MasteryMade CSS
  2. Embed hc-metadata (service identity, capabilities, compliance tier)
  3. Embed hc-instructions (behavioral rules for AI consumers)
  4. Embed hc-context-public (I/O schemas)
  5. Publish to plan.jasondmacdonald.com/manual/[skill-name]
  6. Register in command center
  7. Update services table: manual_path, hc_url, updated_at

12.5 Priority Ordering

PrioritySkillsCountRationale
1 (foundation)calibrate, handoff, morning-kickstart, session-close4Standalone, daily use
2 (operating system)321-exec, 321-framework-jason, jason-guardian, 2026-execution4Personal framework, high usage
3 (content)jason-writer, jason-editor, blue-ocean, linkedin-growth, prompt-architect5Content pipeline (PRD 8)
4 (expert pipeline)expert-research, expert-doc-processor, expert-clone-scorer, expert-test-extractor, expert-os-deployment5Core extraction (PRD 4)
5 (infrastructure)n8n-builder + 6 n8n skills7Build infrastructure
6 (specialized)meta-arch, arch, leverage, meeting trackers, extract-to-lists6Lower frequency

Total: 31 skills across all tiers.

12.6 Post-Generation Integration

  1. Org registry services table has all skills registered
  2. plan.jasondmacdonald.com/manual/ has page per skill
  3. Master Registry Section 12 updatable: MANUAL.md column → links
  4. Any skill discoverable via registry query
  5. Future skills auto-generate MANUAL.md on creation (enhance skill-creator)

12.7 Acceptance Criteria

MASTERYMADE — PRD 12 of 12

Dominia Facta. Build what compounds.