andonimichael/arxitect/architect

Architect

You are orchestrating a feedback loop that ensures code meets object-oriented design, clean architecture, and API design standards.

The loop alternates between two phases:

1. Implement — a Code Implementer agent writes or modifies code
2. Review — the arxitect:architecture-review skill dispatches all

three design reviewers and returns a combined report

The user's request: $ARGUMENTS

Process

Follow these steps exactly. Do not skip or combine steps.

Step 1: Prepare Context

Read these orchestration files (not the reviewer reference material — each reviewer reads its own):

• skills/architect/review-output-format.md
• skills/architect/approval-criteria.md

Step 2: Implement

Detect the best available implementation strategy and use it. Check in this order:

Strategy A: Superpowers (preferred)

Check whether the superpowers plugin is installed by looking for superpowers skills in your available skills list (skills with a superpowers: prefix).

If superpowers is available, use its planning and execution workflow:

1. Use the superpowers planning skill to break the task into discrete,

verifiable steps

1. Use the superpowers execution skill to implement each step
2. Tell the implementer to read

skills/architect/implementer-prompt.md for design guidelines

1. Provide the user's task description and any review feedback from prior

iterations

Strategy B: Native Agent

If superpowers is not installed, check whether the Agent tool is available.

If it is available:

1. Read the relevant files yourself, then write a concise implementation plan

as a regular chat message — do not use `EnterPlanMode`. Format it with markdown headings: Overview, Changes, Testing, and Verification steps.

1. Fork a Code Implementer agent with full tool access (Read, Write, Edit, Bash,

Glob, Grep). Tell it to read skills/architect/implementer-prompt.md for its guidelines, then provide:

• The user's task description
• The plan produced above
• Any review feedback from prior iterations

Strategy C: Direct implementation (fallback)

If neither superpowers nor native plan + agent tools are available, implement the changes directly:

1. Read skills/architect/implementer-prompt.md for design

guidelines

1. Design the component structure before writing code
2. Implement the changes yourself using available file tools

Regardless of strategy, provide the following context on the first iteration: "This is the first iteration. No review feedback yet." On subsequent iterations, provide the feedback document from Step 4 instead.

Collect the implementer's output: files changed and design decisions made.

Step 3: Architecture Review

Run the arxitect:architecture-review skill on the list of files the implementer created or modified. It dispatches all three reviewers (Object Oriented Design, Clean Architecture, API Design) and returns a combined report with verdicts and structured findings.

Step 4: Evaluate

Check all review verdicts:

All APPROVED: The loop is complete. Proceed to Step 6.

Any CHANGES_REQUESTED: Compile a feedback document from the combined review report:

## Review Feedback — Iteration [N]
 
### Object Oriented Design Findings
[CRITICAL and WARNING findings with ID, description, files, recommendation]
 
### Clean Architecture Findings
[CRITICAL and WARNING findings with ID, description, files, recommendation]
 
### API Design Findings
[CRITICAL and WARNING findings with ID, description, files, recommendation]
 
### Previously Addressed
[Finding IDs fixed in prior iterations, to prevent regression]
 
### Iteration History
- Iteration 1: [summary]
- Iteration 2: [summary]

Check the safety valve: if this was iteration 3, proceed to Step 5. Otherwise, return to Step 2 with the feedback document as review feedback.

Step 5: Safety Valve

Three iterations have completed. Check remaining findings:

• If CRITICAL findings remain: Present them to the user with this

message: "The architect has completed 3 iterations. The following CRITICAL findings remain unresolved: [list]. How would you like to proceed?"

• If only WARNING or SUGGESTION findings remain: Auto-approve with

caveats. Proceed to Step 6 but note the remaining findings as accepted trade-offs.

Step 6: Complete

Present the final summary to the user:

1. What was implemented: Brief description of the changes
2. Files changed: Complete list of created or modified files
3. Review iterations: How many iterations and what was resolved in each
4. Design decisions: Key architectural choices and the principles that

guided them

1. Remaining items: Any SUGGESTION-level or accepted WARNING trade-offs

Rules

• Never skip a review. Even if the code looks good, always run the

architecture-review skill. The value is in the systematic evaluation.

• Never modify files during review. Only the implementer modifies code.
• Track finding IDs. Use finding IDs to correlate fixes with findings

and detect regressions across iterations.

Integration

Required skills:

• arxitect:architecture-review — Dispatches all three design reviewers

Optional plugins:

• superpowers — If installed, Step 2 uses its planning and execution

skills for structured implementation. Detected by the presence of superpowers: prefixed skills.

Orchestration files (read by this skill):

• skills/architect/implementer-prompt.md — Guidelines for the

Code Implementer agent

• skills/architect/review-output-format.md — Structured output

format all reviewers must follow

• skills/architect/approval-criteria.md — Verdict rules and

safety valve logic

Alternative workflow:

• arxitect:architecture-review — Use for read-only review without the

implement-iterate loop