executive

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.

Analyze epics and rank by implementation priority using 6-factor weighted scoring from epic, feature, and task data. Factors include task completion (6-state markers), artifact readiness (epic + feature level), dependency readiness, journey progress, implementation readiness (implement skill prerequisites), and blocking value.

Track and update epic progress by scanning artifacts, running compilation to detect error counts, auto-updating tasks.md markers based on build progress AND team inbox state (state.json + TaskList drift detection — same narrow auto-fix as /agile:epic:assign), syncing tasks.md↔spec.md↔epic.md status mismatches, and pushing all updates to Azure DevOps. This skill DISPLAYS a dashboard BUT ALSO automatically UPDATES all artifact files (tasks.md, spec.md, epic.md) and DevOps work items. Use --no-sync only when you want a completely read-only dashboard with NO file writes. Use this skill whenever the user asks about epic progress, status, how far along an epic is, what's left to do, wants a progress report, asks to "update" or "sync" or "refresh" epic status, asks to "fix tasks.md markers" or "fix marker drift", or mentions any combination of "tasks.md", "spec.md", "epic.md" with progress or status. Triggers on: "epic progress", "show progress", "what's blocking", "sync epic status", "update progress", "refresh epi

Final quality gate that comprehensively validates an epic implementation against its design, plan, specs, and tasks before marking it COMPLETED. Dispatches parallel validation agents across 5 domains (artifact consistency, task completion, build verification, constitution compliance, acceptance criteria) and produces a structured PASS/FAIL verdict. Use this skill whenever the user wants to validate an epic, verify epic completion, check if an epic is done, run a final quality gate, confirm all features are implemented, or mentions "validate epic", "verify epic", "epic done?", "close epic", "complete epic", "mark epic completed", or any request to confirm epic implementation correctness. Also use proactively after epic implementation finishes to ensure nothing was missed.

Plan a multi-epic initiative through conversational brainstorming. Produces design.md with strategic context, epic decomposition table, sprint timeline, and cross-epic coordination. Saved to agile/initiatives/NNN-name/. Use when a goal requires 2-7 epics across multiple sprints — bigger than a single epic but more concrete than a product PRD. Triggers on "plan initiative", "break this into epics", "multi-epic project", "sprint planning for a big feature", "decompose into epics", "initiative brainstorm", "group epics", "create initiative", "initiative roadmap". Do NOT use for single-epic scope (use agile-epic-brainstorm) or full product vision (use agile-product-brainstorm).

Pack every markdown artifact in an initiative folder (design.md, refinement-report.md, progress.md) PLUS the full pack for every realized epic in the initiative (invoking agile:epic:pack for each epic in ascending order) 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 initiative artifacts for Google NotebookLM ingestion, generate a single source for Gemini-based infographic / slide deck / video presentation creation covering the whole multi-epic program, prepare an initiative for stakeholder briefing material, or asks to "pack", "combine", "bundle", "consolidate", or "flatten" an initiative's documentation. Strict validation blocks the commit on any context loss.

Track realization + implementation progress for an initiative. Scans the initiative's Epic Candidates table, cross-references with agile/epics/ to find realized epics (accepts canonical `initiative:` frontmatter and legacy prose backlinks), scans each realized epic's tasks.md for 6-state marker counts, and writes a regenerable `agile/initiatives/NNN-name/progress.md` with realization table, per-epic completion %, and unrealized backlog. Use when the user asks about initiative progress, initiative status, "how far along is the initiative", wants a cross-epic dashboard, or mentions the initiative's planned epics vs. realized ones. Triggers on "initiative progress", "initiative status", "how far along is initiative", "initiative dashboard", "check initiative", "refresh initiative progress".

Use when an approved initiative design.md needs expert stress-testing before epic brainstorming. Five expert agents (Proposer, Challenger, Grounder, Reviewer, Critic) run a configurable number of progressive iterations (default 2, up to 5 via `--iterations N`) to strengthen strategy, challenge assumptions, ground in codebase reality, and validate coherence. Produces a refined design.md (status REFINED) and refinement-report.md. Triggers on: "refine initiative", "review initiative design", "stress-test initiative", "challenge initiative", "expert panel for initiative", "improve initiative design", "polish initiative before epics".

Interactive brainstorming session to create, refine, review, and specify a Product Requirements Document (PRD). Guides users through progressive disclosure to capture product vision, target users, features, requirements, and success metrics. Produces a comprehensive PRD saved to agile/product/ that can spawn multiple epics. Use when starting a new product initiative, defining product scope, or creating product specifications before epic planning.

Use when an approved Product Requirements Document (PRD) needs expert stress-testing before initiative brainstorming. Five expert agents (Proposer, Challenger, Grounder, Reviewer, Critic) run a configurable number of progressive iterations (default 2, up to 5 via `--iterations N`) to sharpen product vision, validate users and competitive positioning, stress feature decomposition, ground in codebase reality, and verify metrics-and-risk coherence. Produces a refined prd.md (status REFINED) and refinement-report.md. Triggers on: "refine product", "refine PRD", "review product requirements", "stress-test PRD", "challenge PRD", "expert panel for PRD", "improve PRD", "polish PRD before initiatives", "refine product before epics".

Generate or update a comprehensive progress report for a Product Requirements Document (PRD). Builds the full reference graph from PRD → Initiatives → Epics → Features → Tasks (and the optional direct PRD → Epic shortcut path), cross-validates linkages in both directions, detects orphans and drift, aggregates four-tier metrics (initiative realization, epic realization, implementation, overall), and writes a regenerable progress.md beside the PRD. Read-only over initiative, epic, feature, and task artifacts. Use when the user asks about product progress, product status, "how far along is the product", PRD progress, PRD status, PRD report, product roadmap progress, or wants a cross-initiative product dashboard. Triggers on "product report", "product progress", "PRD progress", "PRD status", "PRD report", "PRD dashboard", "regenerate product report", "product roadmap status", "how far along is the PRD", "product realization", "product implementation", "track all initiatives epics features for PRD", "PRD reference

Authoring + governance tool for SSO Tier-1 code rules in `.claude/rules/` (architecture, code-style/{kotlin,java,typescript,html,scss,frontend}, dependencies, testing, workers). Creates new rule files, refines wording, validates citation integrity, and detects misalignment with the constitution — orphan citations (rule cites missing principle), orphan-range citations, stale citations (cited principle was redefined), missing extractions (constitution principle has code-level guidance with no extracting rule), modality drift (MUST/SHOULD flips), wrong-domain citations, inheritance drift, and registry drift. Orchestrates a five-agent expert team (researcher, thinker, grounder, technical, reviewer) so no code-rule change ships without multi-perspective review and no rule drifts from the constitution unnoticed. Use this skill whenever the user wants to create, update, enhance, refine, validate, list, compare, detect, align, or sync a code rule; whenever they mention `.claude/rules/`, "code style", "naming conventi

Authoring tool for the GSB Federated Constitution Architecture (master + common/services/workers/frontend domain constitutions in .agile/rules/). Creates new domain constitutions, adds/removes/redefines principles, refines wording, validates compliance, compares domains, detects drift, and reconciles the registry. Orchestrates a six-agent expert team (researcher, investigator, thinker, grounder, critic, reviewer) so no constitutional change ships without multi-perspective review. Use this skill whenever the user wants to create, update, refine, enhance, validate, list, compare, detect, or sync a constitution; whenever they mention "constitution", "principle", "MASTER:", "WORKER:", "SERVICES:", "FRONTEND:", "COMMON:", "EPIC:", "amendment", "ratify", "governance", "policy", or "guardrail" in the context of the .agile/rules/ corpus; whenever they ask to add or change project-wide standards/policies/regulations; or whenever they want to bump a constitution version. Also use proactively after any change that affec

Team lifecycle gateway: create, delete, list, add, remove, kill, get, status, prune, message — manages team creation, member spawning, monitoring, messaging, and teardown. Supports pipeline mode (chain multiple commands in one prompt) and batch add (multiple members with 'name1,name2 with agent-type; name3 with agent-type2' syntax).

"This skill should be used when the user mentions "build failed", "pipeline failure", "fix build", "CommonIntegration failing", "entity tests failing", "repository tests failing", or when Azure DevOps build errors are detected. Orchestrates diagnosis and resolution of Azure DevOps build failures with intelligent agent routing and task tracking."

Azure DevOps work item management with subcommands for CRUD operations, querying, and bidirectional sync between local agile artifacts and Azure DevOps. Use this skill whenever the user wants to interact with Azure DevOps work items — creating, reading, updating, searching, listing, or syncing. Triggers on: "devops workitem", "get workitem", "create workitem", "update workitem", "search workitem", "list workitems", "push to devops", "pull from devops", "sync devops", "show sprints", "show areas", "show tags", "workitem types", "devops get", "devops create", "devops push", "devops pull", "devops sync", "check drift", "sync epic", "sync feature", or any request involving Azure DevOps work items.

Intelligent git commit and push with automatic conflict resolution, smart rebasing, and self-improving capabilities. This skill should be used when committing changes, pushing to remote, handling merge conflicts, or when the user invokes "/git-commit-push", "/git:commit:push", "commit and push", "sync with remote", or mentions git commit/push operations. Learns from each execution to become more efficient.