skills.rest
provenimpact
provenimpactOFFICIAL
Explore all skills by this author →
GitHub

needs-adr

Record and manage Architecture Decision Records with lifecycle and index.

Updated Feb 19, 2026
Search Tags:#architecture#adr#governance#traceability#software-design#decision-record#docs/adrs
One-click install
npx skills add https://github.com/provenimpact/proven-needs --skill needs-adr
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: needs-adr
Source: https://github.com/provenimpact/proven-needs/tree/main/skills/needs-adr
Command: npx skills add https://github.com/provenimpact/proven-needs --skill needs-adr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Architecture Decision Records (ADRs) capture and preserve architectural decisions across projects, ensuring traceability and governance.

Core Features & Use Cases

  • Centralized ADR repository under docs/adrs/ with index and kebab-named files
  • Lifecycle management: create, update, supersede, deprecate, and reference ADRs
  • Cross-linking ADRs to feature designs and governance across feature packages

Quick Start

Create an ADR for a new technology decision using the orchestrator.

Frequently Asked Questions about needs-adr

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

FAQPage Schema
What is an Architecture Decision Record and when do I need one?▼

An Architecture Decision Record (ADR) captures technology decisions at the project level to ensure traceability and governance. You need ADRs during software design to preserve architectural decisions and maintain consistency across feature packages.

How do I create and manage Architecture Decision Records?▼

Create and manage ADRs by placing kebab-named files in a centralized repository under docs/adrs/ with an index. Lifecycle management supports updating, superseding, deprecating, and cross-linking records to feature designs for consistency.

What is the best way to structure ADR files for project governance?▼

The best way to structure ADR files for governance is using a centralized repository under docs/adrs/ with a defined index and kebab-named files. This structure ensures traceability and consistency for architectural decisions.

How do I supersede or deprecate an existing architecture decision?▼

Supersede or deprecate an existing architecture decision using ADR lifecycle management. This process updates the decision record files within the docs/adrs repository, maintaining cross-links to feature designs and ensuring historical traceability.

Does this ADR approach work without external dependencies?▼

Yes, this ADR approach works without external dependencies. It relies on a centralized file repository under docs/adrs/ with an index and kebab-named files, defining the structure and lifecycle internally for decision traceability.

Related Skills

Explore More Software Engineering Skills→
mattjeffersonmattjefferson
4

he-bootstrap

Initialize a repository with Harness Engineering directory structure and baseline documentation files.

Community
Basic
pelcherspelchers

adr-setup

Bootstrap and maintain .adr/ Architecture Decision Record workspaces with templates and lifecycle rules.

Community
Advanced
flight505flight505
4

architecture-research

Evaluate technology options and document decisions with Architecture Decision Records.

Community
Advanced
aurora-atomsaurora-atoms

feature-delivery-case

Maintain an evidence-linked lifecycle record for feature delivery cases.

Community
Advanced