Using Architecture Compiler

Use when starting architecture work and you need to decide whether to compile/finalise architecture or implement an already-approved architecture.

Security Scan

This is an instruction-only routing helper for an architecture-compiler workflow that is internally consistent and requests no credentials, but it assumes a separate compiler repository is present and gives no install instructions.

Purpose & Capability

The name/description match the SKILL.md content: the skill's job is to decide whether to use the 'compiling' or 'implementing' architecture workflows and to enforce gating rules. It references repo-local artifacts (AGENTS.md, tools/, schemas/, config/, patterns/, docs/architecture/) which are relevant to that purpose.

Instruction Scope

Instructions correctly limit actions to reading repo files and routing between two skills. However, they require the full Architecture Compiler repo to be installed and instruct the agent to 'stop and install it before routing further' without providing an installation mechanism or explicit human-confirmation step, which is ambiguous and could let an agent attempt an ad hoc install if not constrained.

Install Mechanism

There is no install spec (lowest-risk format), which is fine for an instruction-only skill — but the runtime instructions explicitly require a full local copy of the compiler repo and say to install it if missing. The lack of a prescribed, trusted install source or human confirmation is a usability/ambiguity risk rather than a direct malicious indicator.

Credentials

The skill requests no environment variables, no credentials, and references only repository-local paths appropriate to its stated purpose. There is no disproportionate secret or credential access.

Persistence & Privilege

always is false and the skill does not request persistent presence or to modify other skills. It allows agent invocation (normal). The SKILL.md advises treating certain directories as read-only unless explicit maintenance is requested.

Assessment

This skill appears coherent and low-risk: it only provides routing and read-only guidance for an architecture-compiler workflow and does not ask for secrets. Before installing or enabling it, ensure you have the full Architecture Compiler repository available locally (and verify its contents) because the skill assumes that repository exists. If the repo is not present, prefer to manually install or review the compiler repo yourself rather than letting an agent attempt an automatic install (the SKILL.md gives no trusted install source). If you are concerned about autonomous agents performing network operations, require human confirmation before the agent tries to fetch or write repository files.

Read This First

Before doing anything else:

1. Read AGENTS.md.
2. Treat tools/, schemas/, config/, and patterns/ as read-only unless the human explicitly asked for compiler-maintenance work in this repo.
3. Decide whether the task is about architecture selection or architecture implementation.

Routing Rule

Use skills/compiling-architecture/SKILL.md when:

• the user wants to turn requirements into architecture decisions
• the user wants to write or refine a spec
• the user wants to compile, recompile, inspect pattern selection, or finalise an architecture
• the user has an existing prototype or codebase and needs to compile, validate, or re-approve the architecture it should converge to
• docs/architecture/ does not exist yet
• docs/architecture/architecture.yaml is missing approval
• implementation planning or coding exposes unresolved provider/runtime/auth/retention/message-path decisions
• any later decision would change constraints.*, constraints.saas-providers, top-level patterns.*, or accepted risk posture
• the user wants existing prototype choices to replace approved providers, boundaries, or selected patterns

Use skills/implementing-architecture/SKILL.md when:

• docs/architecture/architecture.yaml exists
• it is approved
• the task is to write code that follows that architecture
• the task is to refactor an existing prototype or codebase so it conforms to the approved architecture
• provider/runtime bindings are already concrete enough that coding will not silently replace the approved contract

Hard Stops

• If the full Architecture Compiler repo is not installed in a stable local path, stop and install it before routing further. Installing only copied skill files is not enough; the workflows depend on tools/, schemas/, config/, and patterns/.
• If no application repo exists yet, do not write app architecture artifacts into the compiler repo.
• If an implementation task lacks approved architecture, stop and switch to the compiling skill.
• If planning starts under the implementing skill and reveals unresolved architecture-binding choices, stop and route back to the compiling skill before more planning or coding.
• If a previously approved architecture is recompiled or materially changed, treat the old approval as invalid until the human re-approves the new output.
• If the user is asking to change compiler behavior or the pattern registry itself, this is compiler-maintenance work, not normal skill usage.

Output

After choosing, explicitly say which of the two skills you are using and why.