Analyze cross-component changes with alternatives and blast-radius assessments.
npx skills add https://github.com/crewrig/crewrig --skill architect-crewrig
Please help me install this Agent Skill. Skill: architect Source: https://github.com/crewrig/crewrig/tree/main/artifacts/core/skills/architect Command: npx skills add https://github.com/crewrig/crewrig --skill architect-crewrig
The architect skill helps you slow down at the right moment when a change may affect multiple components, shared contracts, migrations, or architectural direction. It prevents rushed decisions by forcing clear framing, alternatives, and ripple-effect analysis before implementation proceeds.
Ask the architect skill to compare two implementation options for a change that affects more than one component and recommend the safer design.
High-intent search queries and answers about installing and using this skill.
To analyze ripple effects for a cross-component refactor, assess the blast-radius by identifying impacted files, shared contracts, and downstream consumers. This requires explicit framing and grounded claims to ensure external surfaces are traceable to repository evidence.
Writing an Architecture Decision Record for a new abstraction requires comparing at least two viable alternatives. You must evaluate their trade-offs, costs, benefits, and reversibility to ground your design decisions before implementation proceeds.
A design review for a system migration is needed when changes cross component boundaries or affect shared contracts. This prevents rushed decisions by forcing explicit framing, ripple-effect assessment, and grounded claims about external surfaces.
To compare architectural trade-offs for an API change, surface at least two viable approaches and evaluate their costs, benefits, and reversibility. This ensures your design review includes grounded decision-making based on repository evidence.
An RFC assessing the blast-radius of a new API should include explicit framing, at least two alternatives, and an analysis of impacted files and downstream consumers. Claims about external surfaces must be traceable to repository context.
mietheDistill software repositories into evidence-grounded context artifacts with structured tracking.
CarlosQ96Generates Architecture Decision Records with rationale, trade-offs, and outcomes from user input.
AltimateAIIdentify downstream consumers and column-level lineage for changed dbt models.
TMI-appsAutomate a three-phase plan, implement, and validate workflow for small tasks.
