Perform adversarial design reviews for cross-service software changes.
npx skills add https://github.com/highflame-ai/ai-factory --skill grill-feature
Please help me install this Agent Skill. Skill: grill-feature Source: https://github.com/highflame-ai/ai-factory/tree/main/skills/grill-feature Command: npx skills add https://github.com/highflame-ai/ai-factory --skill grill-feature
This skill prevents costly architectural drift and structural ambiguity by forcing a rigorous, adversarial review of high-stakes changes before any implementation begins.
Invoke the grill-feature skill to perform an architectural review on your proposed cross-service feature change.
High-intent search queries and answers about installing and using this skill.
To review architecture for cross-service changes, perform an adversarial design review that interrogates scope, platform invariants, and shared contracts. This process anchors decisions in project-specific documentation like ADRs to uncover hidden structural risks.
Adversarial design review is a rigorous interrogation process that evaluates high-stakes architectural changes before implementation. It systematically interviews stakeholders to uncover hidden risks in cross-service contracts, authz schemas, and platform invariants using established checklists.
Document architectural decisions by capturing the design review outcomes as spec-registry entries, ADR drafts, or PR-ready assumption blocks. This ensures design intent is preserved and prevents structural ambiguity during implementation.
You need an architectural review for spec-driven development when proposing cross-service, contract-touching, or platform-invariant changes. It prevents costly architectural drift by forcing a rigorous evaluation of scope and shared contracts before implementation begins.
Yes, you can validate high-stakes software changes by anchoring the review in existing architecture docs, ADRs, and established checklists. This evidence-based approach ensures design decisions are grounded in project-specific documentation rather than memory.
The best way to prevent architectural drift is to mandate an adversarial design review that interrogates cross-service contracts and platform invariants before implementation. Capturing these decisions in ADR drafts and spec-registry entries preserves structural integrity.
asermaxGenerate ADR or DES drafts documenting architectural decisions from codebases.
sertaoseracloudRecord architectural decisions and rationale in ADR templates.
sarimofficialEvaluate hackathon submissions against project specs and judging criteria.
rajyeole6Audit smart contracts for reentrancy, oracle manipulation, and access control vulnerabilities.
