skills.rest
Zaba505
Zaba505COMMUNITY
Explore all skills by this author →
WebsiteGitHub

plan-adrs

Enumerates architectural decisions from technical requirements and files one GitHub issue per ADR.

1|Updated Mar 7, 2023
Search Tags:#planning#documentation#adr#github issues#gh cli#architecture decisions#technical requirements
One-click install
npx skills add https://github.com/Zaba505/infra --skill plan-adrs-zaba505
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plan-adrs
Source: https://github.com/Zaba505/infra/tree/main/.claude/skills/plan-adrs
Command: npx skills add https://github.com/Zaba505/infra --skill plan-adrs-zaba505

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Drafting Architecture Decision Records one at a time without first listing the full set leads to contradictory ADRs that must be rewritten when sibling decisions are made. This skill turns a reviewed tech-requirements.md into a confirmed list of architectural decisions and files one trackable GitHub issue per ADR. ## Core Features & Use Cases - Review Gate Enforcement: Refuses to run unless tech-requirements.md has a reviewed_at date newer than its last modification, preventing planning against unreviewed drafts. - Decision Enumeration: Clusters TR-NN requirements into discrete ADR-worthy decisions, rejects bundled mega-ADRs, and flags cross-capability decisions that belong in the shared ADR namespace. - GitHub Issue Filing: After human approval, files one issue per ADR via gh issue create using the story(adr) title convention, wires blocked-by dependencies, and places issues on the project board with milestone and Area fields. - Use Case: After reviewing technical requirements for a multi-tenant platform capability, invoke this skill to produce a confirmed list like "tenant state storage location", "partitioning scheme", and "access pattern", each filed as its own issue ready for the define-adr skill. ## Quick Start Ask the assistant to plan the ADRs for your capability, for example: "Plan the ADRs for the self-hosted-application-platform capability using its reviewed tech-requirements.md."

Frequently Asked Questions about plan-adrs

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

FAQPage Schema
How do I plan ADRs for a capability before writing them?▼

Invoke the skill with a phrase like "plan ADRs for {capability}" after its tech-requirements.md is reviewed. It enumerates each architectural decision with the TR-NNs it addresses, waits for your approval, then files one GitHub issue per ADR.

Why does the skill refuse to plan ADRs for my capability?▼

It stops when tech-requirements.md has reviewed_at set to null or older than the file's last modification. Review the current contents, set reviewed_at to today's ISO date, and re-invoke the skill.

Can I bundle multiple decisions into one ADR?▼

No. The skill rejects bundled ADRs because bundling dilutes rationale and prevents superseding one sub-decision without revisiting the others. It proposes splitting into separate ADRs, one decision per issue.

What happens to cross-capability decisions like networking or identity?▼

Decisions that ripple across capabilities are flagged and excluded from the capability-scoped list. They belong as shared ADRs in docs/content/r&d/adrs/ through a separate flow, and no capability-scoped issue is filed for them.

Does this skill draft the ADR content itself?▼

No. It only enumerates decisions and files planning issues. Each issue references the define-adr skill, which authors one ADR per invocation by proposing options tied to the TR-NNs and stopping for a human decision.

What GitHub permissions are needed to file ADR issues?▼

The gh CLI needs the repo scope for issue creation plus the project scope for board operations, obtained via gh auth refresh -s project. Milestones and Area field values are read live and never invented.

Related Skills

Explore More Software Engineering Skills→
narcisolcfnarcisolcf

pca-docs

Generate formal .docx documents from PCA data using templates and tracked changes.

Community
Advanced
jeremyaryjeremyary
7

adr

Create structured Markdown Architecture Decision Records in the plans/adr/ directory.

Community
Intermediate
wooyekwooyek

dev10x-adr

Generate Architecture Decision Records with PlantUML diagrams and project conventions.

Community
Advanced
GongYuanCaiJiGongYuanCaiJi

octopus-quick

Executes small ad-hoc code changes with atomic commits and summary tracking.

Community
Intermediate