Agent-Skills.md

Agent Skills: Architecture Gate Reviewer

Internal Moonshot Architecture stage for reviewing whether an architecture package is ready for implementation handoff.

UncategorizedID: munlucky/claude-settings/architecture-gate-reviewer

Repository

munlucky/claude-settings
munlucky

Install this agent skill to your local

pnpm dlx add-skill https://github.com/munlucky/moonshot-relay/tree/HEAD/skills/architecture-gate-reviewer

Skill Files

Browse the full folder contents for architecture-gate-reviewer.

Download Skill

Loading file tree…

skills/architecture-gate-reviewer/SKILL.md

Skill Metadata

Name
architecture-gate-reviewer
Description
Internal Moonshot Architecture stage for reviewing whether an architecture package is ready for implementation handoff.

Architecture Gate Reviewer

Role

Review an architecture package before implementation handoff and block readiness claims when required evidence is missing.

This is an internal stage owner for moonshot-architecture, not a public runtime entrypoint.

Inputs

  • Architecture package artifacts
  • Validator output
  • Traceability matrix
  • Handoff target and planned owned/read-only/staged paths
  • APPLICABLE_KNOWLEDGE_SLICE when architecture-heavy work depends on project knowledge, KG, ontology, or knowledgeAnchors
  • ARCHITECTURE_CONTRACT_SLICE and ARCHITECTURE_HANDOFF when execution handoff should be contract-bound

Flow

  1. Check required artifacts for the selected mode.
  2. Check validator output and unresolved structural errors.
  3. Check traceability from requirements to ASRs, ADRs, owners, and verification signals.
  4. Check Brownfield compatibility, migration, and rollback evidence when applicable.
  5. For architecture-heavy work, check contract slice and handoff status before implementation handoff.
  6. Return pass, needs-more-evidence, or block with concrete findings.

Hard Stops

  • Do not approve a package that fails architecture-artifact-validate.mjs.
  • Do not approve implementation handoff without owners and verification signals.
  • Do not approve architecture-heavy implementation handoff without ARCHITECTURE_CONTRACT_SLICE and ARCHITECTURE_HANDOFF.
  • Do not approve a blocked ARCHITECTURE_HANDOFF or one missing selected constraints, path boundaries, or verification signals.
  • Do not approve handoff when a blocking ontology constraint is absent from the contract or lacks an enforcement rule.
  • Do not treat review notes as runtime-state completion authority.
  • Do not hide blocker findings in summary text.

Required Evidence

  • Review status.
  • Findings with artifact paths.
  • Validator output reference.
  • Handoff readiness decision and residual risks.