Menu
SkillsMP has collected 11 skills from DanMcInerney/architect-loop. Open a skill to review its source and details.
Showing 11 of 11 collected skills.
Use when the user asks to architect-fast a change, run the light factory lane, or factory-build a small goal — a few files, roughly one sitting, at most ~3 parallel issues — into a specced plan with parallel builders, one builder-performed closing…
Use when the user asks to architect, run or continue the autonomous software factory, turn a goal into a hardened tracker issue plan, dispatch builder jobs, grade finished work, diagnose blockers, or finish a factory run.
Shared vocabulary for designing deep modules and for naming factory concepts consistently. Load before writing a spec, decomposing issues, freezing checks, or reviewing a diff - anywhere "module," "interface," "issue," or "frozen check" need to mean the same…
Use when the architect factory orchestrator dispatches a fresh strategist subagent to harden a draft spec: falsify it with file:line evidence, fold the surviving findings into a revised spec, decompose it (issues plus checks), and stress-test its own…
Use for the closing whole-run review in the architect factory — the only model review in the loop: dispatched by the orchestrator, at finish, to one fresh strategist subagent that audits the entire run diff for defects only isolated parallel slices can…
Use when decomposing a hardened spec into tracker issues: cutting tracer-bullet vertical slices through every layer, ordering structural work first with blocking edges, maximizing the disjoint parallel frontier, publishing producer/consumer interface…
Spec-writing stage skill for the architect factory: synthesizes the run's conversation, repo evidence, and research findings into `docs/spec/<run>.md` after grounding. Invoked by the strategist subagent the orchestrator dispatches during `/architect` intake —…
Use when the strategist drafts per-issue graded checks after decomposition and before builder dispatch. Produces one check file per issue at `docs/checks/<run>/<slice>.md`, frozen in git, read-only after.
Factory-context integrate stage (end-of-run shipping) for one dedicated builder subagent dispatched by the orchestrator after the fix wave has merged, after a GREEN verdict, or after a recorded ruling skips the review. First step is the docs pass — update…
Use when the user asks for discovery-scale research that informs a decision: brainstorming a project or feature, choosing a technology, or requests like "research X", "what's the state of the art", or "deep research". Use this skill to turn broad, uncertain…
Test-driven development for factory builders. Use when a ship job implements at the issue's pre-agreed seams — the red -> green loop, one test then one minimal implementation per cycle, never a refactor while RED.