Orchestrates a complete clean-room reverse engineering process that produces legally-defensible Product Requirements Documents (PRD), artifacts across all four agile levels (initiative → epic → feature → user story), and formal team separation for handoff to an independent implementation team. Operates at EPIC scope (against a codebase path) or INITIATIVE scope (against an approved initiative design.md, looping over its Epic Candidates table). Plugs into the initiative workflow via canonical `initiative:` frontmatter so `agile-initiative-progress` can track realization and task completion on one dashboard. Use when you need independent specifications for a development team with no access to original source, or when you want to reverse-engineer every epic in a multi-epic initiative in one coordinated run. Triggers on "clean room", "clean-room reverse engineer", "reverse engineer initiative", "reverse engineer epic", "generate PRD from codebase", "legally clean spec", "spec team vs impl team", "reverse engineer
Validates artifacts against the GSB Federated Constitution Architecture. Detects affected domains from artifact content, loads relevant constitutions (master + domain-specific), and checks principle ID references for compliance. Used by epic and feature journey commands as a compliance gate.
Combine multiple markdown section files into a single merged document (.md and .pdf). Use when the user wants to merge, combine, consolidate, or generate a single document from sectioned files — for PRDs, design docs, specs, runbooks, or any multi-section markdown project. Triggers on requests to "combine documents", "merge sections", "generate combined doc", "export as single PDF", "merge markdown files", "combine PRD sections", "consolidate doc sections". Works with any directory of markdown section files. Pass the source directory containing section files as the first argument, and optionally the destination directory as the second argument (defaults to same as source).
Dispatch the next wave of epic tasks into the team inbox without re-running the full implement flow. Use this when the team-lead session's inbox has drained mid-epic and you need to push the next round of tasks into team members. The skill reads state.json + tasks.md, categorizes the inbox, advances the wave pointer if the current feature is done, then either assigns existing pending tasks (fast path) or creates the next feature's tasks via TaskCreate + TaskUpdate(addBlockedBy) + SendMessage assignment (re-populate path) using the same contracts as agile:epic:implement. Requires an active team-lead session with an existing team and an in-flight epic (state.json present, epicStatus=PENDING or IMPLEMENTING). Triggers on "/agile:epic:assign", "assign tasks to team", "assign tasks to team members", "assign next wave", "push tasks to inbox", "dispatch next round", "team inbox empty assign more", "next wave of tasks", "populate inbox". Do NOT use for fresh epic kickoff (use /agile:epic:implement) or for marking the
Turn epic ideas into approved designs through conversational brainstorming. Produces design.md in a new epic directory. Replaces the idea and prompt commands.
Orchestrates epic implementation as a team lead by parsing epic structure, building feature dependency graphs, and delegating features to existing teammates through the team inbox system (TaskCreate/TaskUpdate with addBlockedBy) and SendMessage notifications. Features execute in dependency order with parallel capability. Each completed task is cross-validated by a different teammate with a max 3-retry correction cycle. The team lead never writes code — it only coordinates. Supports session resume via state.json for crash recovery. Use this skill when the user wants to implement an epic, execute features, or delegate epic work to a team. Triggers on: "implement epic", "execute epic", "run epic", "start epic implementation", "delegate features", or any request to orchestrate multi-feature implementation with team coordination.
Pack every markdown artifact in an epic folder (epic.md, plan.md, design.md, checklist.md, and every feature's spec.md + tasks.md) into a single NotebookLM-ready source document at NNN-pack.md, then strictly validate that no content was lost in translation. Use this whenever the user wants to combine epic artifacts for Google NotebookLM ingestion, generate a single source for Gemini-based infographic / slide deck / video presentation creation, prepare an epic for stakeholder briefing material, or asks to "pack", "combine", "bundle", "consolidate", or "flatten" an epic's documentation. Strict validation blocks the commit on any context loss.
Interactively refine an epic strategic plan from approved design.md, then generate complete epic structure — epic.md, feature specs, and task lists. After generation, performs cross-artifact consistency analysis to detect misalignments, then auto-remedies findings before commit. Use when planning a new epic after brainstorm approval.