skills.rest
Moffran
MoffranCOMMUNITY
Explore all skills by this author →
GitHub

ce-adr-consult

Identify applicable ADRs and extract binding constraints from docs/improvement/adrs/.

78|15|Updated May 1, 2023
Search Tags:#adr#compliance#governance#risk-management#change-management#architecture-decision-record#software-planning
One-click install
npx skills add https://github.com/Moffran/calibrated_explanations --skill ce-adr-consult
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ce-adr-consult
Source: https://github.com/Moffran/calibrated_explanations/tree/main/.claude/skills/ce-adr-consult
Command: npx skills add https://github.com/Moffran/calibrated_explanations --skill ce-adr-consult

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

ADR governance can be ambiguous when multiple ADRs apply to a proposed change. This skill maps the applicable ADRs and extracts their binding constraints to ensure decisions are followed and conflicts with the release plan are avoided.

Core Features & Use Cases

  • Identify which ADRs govern a proposed change.
  • Extract and summarize binding constraints from ADR documents.
  • Prioritize ADR decisions over the release plan when conflicts arise and ignore superseded ADRs.

Quick Start

Consult the ADRs for the proposed change and extract their binding constraints before implementing the plan.

Frequently Asked Questions about ce-adr-consult

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I identify which Architecture Decision Records govern a proposed software change?▼

To identify governing Architecture Decision Records, scan ADRs stored under docs/improvement/adrs/ to determine applicability to the proposed change, checking that the ADR status is not superseded before applying its constraints.

What is the process for extracting binding constraints from ADRs during change management?▼

Extracting binding constraints involves reading the Decision section of applicable ADRs and cross-referencing the Consequences section to ensure software planning aligns with established governance and avoids release plan conflicts.

How do I handle conflicts between ADR decisions and my release plan milestones?▼

When conflicts arise between ADR decisions and release plan milestones, prioritize the ADR decisions over the release plan and note the relevant milestones to ensure compliance and proper risk-management.

Should I consider superseded ADRs when evaluating governance compliance for a new feature?▼

No, you should ignore superseded ADRs when evaluating governance compliance. You must check the ADR status first and only extract binding constraints from active records to ensure valid software planning.

What directory structure is required for consulting ADRs before implementing changes?▼

Consulting ADRs requires storing your Architecture Decision Records under the docs/improvement/adrs/ directory structure so the skill can accurately parse status, Decision, and Consequences sections.

Related Skills

Explore More Software Engineering Skills→
TraftGTraftG
33

architecture-decision

Generate ADR-XXXX files with Context, Decision, Consequences, and Alternatives sections.

Community
Advanced
reason-healthcarereason-healthcare
12

rh-inf-resolve

Resolve open conflicts across extract-plan.yaml and formalize-plan.yaml before implementation.

Official
Advanced
abdullah1854abdullah1854
1

session-handoff

Generate Markdown Architectural Decision Records from structured inputs.

Community
Intermediate
avgarciaavgarcia

adr-review

Review architecture decision records for missing decisions, risks, and structural gaps.

Community
Advanced