Design sprint architecture documentation and reviewer checklists with pass/fail adjudication.
npx skills add https://github.com/robconery/crap-code --skill architect-robconery
Please help me install this Agent Skill. Skill: architect Source: https://github.com/robconery/crap-code/tree/main/.pi/skills/architect Command: npx skills add https://github.com/robconery/crap-code --skill architect-robconery
It prevents weak or inconsistent technical decisions by turning sprint inputs into a clear architecture plan, an enforceable reviewer checklist, and a closing architectural verdict.
/docs/sprint/{name}/architecture.md with components, ports, data flow, and named pattern justifications, explicitly covering hex-lite layering, CQS, and SRP compliance./docs/sprint/{name}/reviewer-checklist.md as a pass/fail gate layered on top of /docs/styleguide.md.Use the architect skill to generate /docs/sprint/{name}/architecture.md and /docs/sprint/{name}/reviewer-checklist.md for a given sprint named {name}.
High-intent search queries and answers about installing and using this skill.
A binary reviewer checklist enforces pass/fail governance gates layered on top of your styleguide.md. It provides a concise enforcement mechanism for sprint-close architectural adjudication, ensuring implementation matches the approved technical approach before final approval.
You need to write an ADR when cross-file or cross-sprint architectural decisions occur during sprint execution. The process tracks decision rationale and signals changes by outputting Drizzle schema diffs for any database schema modifications, ensuring architectural shifts are documented and traceable.
For repeated task failures, a strike-3 escalation directive reviews the approach versus the implementation failure mode after three failures. It issues a concise directive for the builder's 4th attempt, focusing on architectural approach validation without writing production code directly.
The best way to validate CQS and SRP compliance is through a sprint-close pass/fail architectural adjudication. This process requires mandatory named pattern justifications and explicit compliance citations in the architecture documentation to ensure architectural readiness before final sprint sign-off.
rarilureloGenerate multi-perspective questions and design-doc templates for pre-implementation reviews.
rajivpantScore code diffs across ten dimensions with PASS, WARNING, or FAIL findings.
lobehubDefine TypeScript database schemas and generate migrations with Drizzle ORM.
EasyCode-ObsidianReview code across seven dimensions and apply user-approved bug fixes.