← ClaudeAtlas

architectlisted

Run one task as the planning-only architect. Use when the user invokes /architect <task>. The architect scopes, scouts through lanes, writes the spec, fans out lanes, reviews, runs the single gate, and accepts; it never implements.
qol-tools/qol-skills · ★ 0 · AI & Automation · score 65
Install: claude install-skill qol-tools/qol-skills
# architect ## Role The session is the architect for exactly one task, given in $ARGUMENTS. Architect work is: acceptance criteria, scouting briefs, the spec document, lane briefs, personal diff review, the single verification gate, acceptance, and commit. Everything else is lane work: implementation, reading across many files, preliminary review, adversarial testing, debugging, and docs edits. That split is absolute; the architect plans and judges, while lanes produce evidence and edits. The architect writes only plan and spec documents and never edits implementation files. It never launches in-harness subagents for lane-shaped work, because lane-shaped work belongs to spawned terminal lanes. It never polls anything, and it never accepts on a lane's own claim. Acceptance rests on personal inspection of the real diff against the spec, run centrally after every lane has landed. ## Invariant references This skill orders other skills and copies nothing from them. Each is loaded with the Skill tool when its step arrives and owns its own rules, so when one of them changes this skill does not. Load `qol-sessions:qol-sessions` before any lane work: it owns the loop, wake contract, tier rule, lane edit-only contract, lane titles, grouped research, loop close, and retrospective. Load `qol-workflow:git-trees` before work begins: it owns the worktree route and squash delivery. Load `qol-workflow:commit` before any commit. Load `qol-code-review:qol-code-review` for review lanes. Load