repo-church

Plugin repo-church in chendrizzy/repo-church. Commands read from the repo's manifest — 1 month ago.

Skills (12)

• church-anchor

  Strengthen Repo Church parent phase anchors before child specs or implementation. Use when the user asks to improve roadmap phases, tighten phase requirements, define parent phase anchors, sequence dependencies, or raise acceptance thresholds before planning. Expects phase ID + Bible packet location

• church-gap-closure

  Close Repo Church gaps, contradictions, and drift with explicit remediation tasks. Use when the user mentions gap closure, planning drift, bible misalignment, unresolved assumptions, failed gates, remediation planning, or contradictory docs/code. Operates the `church ledger gaps` surface; never sile

• church-handoff

  Produce a Repo Church phase handoff with frozen scope, consumed artifacts, validation commands, and next actions. Use for phase handoff, context handoff, resume brief, execution handoff, or preparing another agent to continue work. Renders a deterministic handoff via `church lifecycle handoff`.

• church-harden

  Harden assumptions with local evidence and current research before planning. Use for church harden, assumption validation, research hardening, evidence gate, market-confidence checks, stale claim review, or GSD-style pre-plan risk tightening. Drives the `church ledger assumptions` surface and `churc

• church-intake

  Run Repo Church Bible intake and thin roadmap slicing. Use when the user asks for church intake, bible intake, roadmap from repo-bible, phase discovery, next milestone framing, or a lightweight planning entry point before research hardening. Accepts a Bible packet path; produces a thin roadmap slice

• church-moat

  Identify and define a project's competitive moat with strategic market research, elevator-pitch clarity, sustainability scoring, and Repo Bible integration. Use during greenfield or brownfield project init, market positioning, competitive leverage analysis, defensibility review, or whenever the user

• church-optimizer

  Optimize Repo Church or GSD-like lifecycle workflows for less redundancy, lower token use, and safer parallelism. Use when the user asks to reduce workflow time, reduce token consumption, improve phase parallelism, simplify gates, or tune lifecycle efficiency without weakening reliability. Produces

• church-ship

  Run a Repo Church ship or merge gate with tests, docs, rollback, risk, and Bible alignment. Use when the user asks for ship checklist, merge readiness, release gate, pre-merge review, or phase completion approval. Emits `SHIP_READY: yes|no` and records the final gate via `church lifecycle advance sh

• church-spec-gate

  Review specs and implementation plans against Repo Church gates. Use when the user asks for spec review, plan hardening, PRD acceptance, implementation plan viability, requirement traceability, or stricter pre-execution approval. Verifies spec coverage and emits a gate outcome via `church lifecycle

• church-uat

  Run collaborative Repo Church UAT with stricter phase-progression gates and mutual signoff. Use when the user asks for user testing, collaborative verification, UAT, acceptance walkthrough, mutual approval, must-pass stories, or post-phase validation. Drives the `church ledger uat` surface and `chur

• church

  Orchestrate Repo Church lifecycle workflows around a Repo Bible packet. Use when the user mentions church, repo-bible-driven planning, GSD-inspired phase gates, lifecycle hardening, assumption validation, gap closure, collaborative UAT, phase handoff, ship gate, or wants a stricter planning-to-verif

• repo-bible

  Generates, audits, and refreshes comprehensive repo Bible packets for products, platforms, and projects. Use when the user asks to create a strategic reference packet, commandments, operating doctrine, market-backed roadmap, product constitution, GTM plan, architecture/design doctrine, or reusable r

Slash commands (21)

• /repo-church:church-archive

  Plan artifact cleanup and archival without deleting lifecycle evidence or breaking future handoffs.

• /repo-church:church-atonement

  Debug or remediate failures with a structured diagnosis, risk ledger, gap closure, and recheck path.

• /repo-church:church-bless

  Bless a release or phase completion: ship gate, risk review, rollback, Bible drift check, and final progression decision.

• /repo-church:church-branch

  Plan a PR-safe branch and review scope without mutating git state or hiding planning artifacts.

• /repo-church:church-canonize

  Canonize a phase: tighten parent anchors, spec gates, requirement traceability, Bible alignment, and measurable acceptance before implementation.

• /repo-church:church-commission

  Commission implementation work with frozen scope, execution handoff, workstream map, validation commands, and rollback notes.

• /repo-church:church-confess

  Add an ad hoc requirement, phase idea, gap, risk, or confession into the correct Repo Church ledger without disrupting the active gate.

• /repo-church:church-council

  Show Repo Church status, available workflows, reasoning boundaries, blocker ledgers, and recommended next command.

• /repo-church:church-discern

  Harden assumptions and ambiguity before phase planning using evidence ledgers, current research, and Bible/market source checks.

• /repo-church:church-fellowship

  Run collaborative verification: peer review, UAT ledger checks, mutual signoff, and user-visible acceptance before phase progression.

• /repo-church:church-gather

  Start or resume Repo Church project intake: initialize state, define or refresh the moat, inventory Bible artifacts, and choose the next gate.

• /repo-church:church-guard

  Plan, check, and scaffold runtime hook coverage with agent-agnostic fallbacks and explicit review gates.

• /repo-church:church-inbox

  Capture and triage inbox or backlog items into typed Repo Church records before routing them to ledgers or gates.

• /repo-church:church-profile

  Capture consented profile signals for workflow personalization while keeping interpretation agent-led and auditable.

• /repo-church:church-quick-rite

  Handle a small, low-risk task without invoking the full Repo Church cycle, while preserving optional state or ledger breadcrumbs.

• /repo-church:church-renew

  Refresh the Bible, lessons, roadmap implications, and next cycle state after a phase, milestone, or strategic change.

• /repo-church:church-rewind

  Plan guarded undo or rollback operations with git evidence, risk warnings, and explicit execution review.

• /repo-church:church-sketch

  Register creative sketch and design artifacts with doctrine links, signoff requirements, and acceptance routing.

• /repo-church:church-survey

  Survey brownfield code, architecture, interfaces, and graph/map evidence before anchoring or major implementation work.

• /repo-church:church-thread

  Manage portable thread and continuation records with handoff links, runtime identifiers, and resume hints.

• /repo-church:church-workspace

  Manage portable Repo Church workspace records for concurrent work without relying on one agent runtime.

Subagents (24)

• church-ai-eval-planner

  AI behavior and evaluation planning specialist; use when a phase builds or depends on AI, LLMs, agents, rankings, recommendations, extraction, or generation.

• church-anchor-architect

  Parent phase anchor and roadmap sequencing specialist; use before specs to ensure phase scope, dependencies, non-goals, and acceptance criteria are strong enough.

• church-archive-steward

  Archive and cleanup specialist; use for completed phase artifact cleanup, retention checks, and non-destructive archive planning.

• church-bible-scribe

  Repo Bible synthesis and doctrine updater; use for Bible generation, refresh, doctrine drift, market-backed requirements, and HTML workbench review.

• church-code-examiner

  Code quality and implementation review specialist; use for changed-code review, regression risk, test adequacy, and implementation drift from spec.

• church-codebase-cartographer

  Brownfield codebase mapping and architecture evidence specialist; use before planning architecture-sensitive or unfamiliar implementation work.

• church-debug-examiner

  Debugging and forensic investigation specialist; use for failed gates, regressions, test failures, unexplained behavior, and root-cause analysis.

• church-doc-scribe

  Documentation and handoff writer; use for docs updates, milestone summaries, renewal reports, and implementation-to-Bible narrative alignment.

• church-doctrine-auditor

  Bible alignment and doctrine drift auditor; use when specs, implementation, UX, or GTM may conflict with the Repo Bible.

• church-gap-steward

  Gap closure and remediation specialist; use when failed gates, contradictions, weak requirements, or unresolved risks need closure tasks and proof.

• church-git-steward

  Git hygiene specialist; use for branch planning, undo planning, rollback risk, and review-scope isolation.

• church-moat-scout

  Market and competitive moat researcher for Repo Church; use for moat definition, competitor mapping, why-now evidence, and defensibility validation.

• church-profile-counselor

  Consented profile and personalization specialist; use for workflow personalization signals, consent review, and behavioral inference boundaries.

• church-runtime-guardian

  Runtime hook and fallback specialist; use for hook planning, adapter risk review, and cross-agent enforcement design.

• church-security-examiner

  Security and privacy review specialist; use for auth, secrets, data, payments, permissions, destructive operations, or compliance-sensitive work.

• church-ship-steward

  Release readiness and ship-gate specialist; use before merge, release, or phase completion to verify risk, rollback, ledgers, and Bible alignment.

• church-sketch-curator

  Sketch and creative artifact specialist; use for design exploration artifacts, acceptance routing, and doctrine/signoff mapping.

• church-spec-canonist

  Strict spec and plan audit specialist; use for pre-execution spec gates, requirement traceability, acceptance thresholds, and plan-review convergence.

• church-thread-steward

  Thread continuation specialist; use for thread records, stale context checks, resume hints, and handoff quality.

• church-triage-steward

  Inbox and backlog triage specialist; use for incoming ideas, questions, risks, backlog items, and scope routing.

• church-uat-fellow

  Collaborative UAT and mutual signoff facilitator; use for post-execution verification, user-story acceptance, peer review, and phase-progression approval.

• church-ui-examiner

  UI/UX verification specialist; use for frontend phases, visual quality, accessibility, responsive behavior, design doctrine, and subjective user-facing acceptance.

• church-workspace-steward

  Workspace management specialist; use for workspace records, active workspace routing, and safe concurrent workspace hygiene.

• church-workstream-deacon

  Workstream decomposition and safe parallelism specialist; use during handoff/commissioning to split execution without conflicts.

Similar plugins