Create auditable Agent Decision Records with role-gated review workflows.
npx skills add https://github.com/me2resh/apexyard --skill decide-me2resh
Please help me install this Agent Skill. Skill: decide Source: https://github.com/me2resh/apexyard/tree/main/.claude/skills/decide Command: npx skills add https://github.com/me2resh/apexyard --skill decide-me2resh
This Skill prevents untracked, ad-hoc architecture choices by forcing structured technical decision-making and producing an Agent Decision Record (AgDR) every time.
docs/agdr/ using an adopters’ overridden template when present.Ask for a decision like: decide between deploying a new service as a standalone Lambda or as part of an existing service, considering scalability, cost, and deployment complexity.
High-intent search queries and answers about installing and using this skill.
To document technical decisions and prevent ad-hoc architecture choices, you can enforce structured technical decision-making that generates an auditable Agent Decision Record. This requires listing 2–4 options with pros and cons and a mandatory justification clause.
An Agent Decision Record is an auditable file created under a project's docs/agdr folder to track technical decisions. You need one for new services, tech stack changes, integrations, major data model changes, and security-sensitive decisions to ensure architecture governance.
To enforce role-based review for technical decisions involving auth or PII, you activate a Tech Lead, escalate to a Head of Engineering for major thresholds, and require a Security Auditor sign-off. This role-gated accountability ensures secure architecture governance.
Yes, you can use custom templates for technical decision records. The system generates the auditable AgDR file using a portfolio-resolved template, automatically applying an adopter's overridden template when one is present in the project.
The best way to structure options and justification for a new tech stack element is to enforce an options table with 2–4 choices, precise ISO-8601 timestamps, title-based slugging, and a mandatory 'because' clause for justification.
michael-watsonAnalyze codebase architecture, dependencies, and constraints into a research document.
AAbdulghanyGenerate auditable Agent Decision Records for engineering decisions.
nuoyanruoshuiDocument technical decisions as structured Architecture Decision Records with context and alternatives.
ChrstprJohnDocument and manage Architecture Decision Records with Markdown templates and frontmatter metadata.