Help us improve
Share bugs, ideas, or general feedback.
From adrs-management
Identifies potential ADRs in specified modules using codebase mapping and git history, generating scored markdown files in must-document/ and consider/ priority folders.
npx claudepluginhub devfullcycle/claude-mkt-place --plugin adrs-managementHow this command is triggered — by the user, by Claude, or both
Slash command
/adrs-management:adr-identifyThe summary Claude sees in its command listing — used to decide when to auto-load this command
Launches the `adr-analyzer` agent to identify potential ADRs in specified modules. When multiple modules are specified, launches agents in parallel for faster analysis. **Prerequisites**: Run `/adr-map` first if mapping.md doesn't exist in the output directory. **What it does**: - Analyzes specified module(s) with strict architectural filtering - Executes multiple modules in parallel when 2+ modules are specified - Uses git history internally to enrich potential ADRs with temporal context - Creates individual ADR files in priority-based folders (NO numbers in filenames) - Weaves git insi...
/discoverScans the local repository for patterns and anti-patterns, then drafts an Architecture Decision Record PRD (pdr.draft.md). Use for a fast preview before a full deep-research run.
/adrGenerates a new Architecture Decision Record (ADR) documenting a technical decision, numbers it sequentially from existing ADRs, researches codebase context, and creates the Markdown file in docs/adr/.
/decisionManages architectural decision records — list, inspect health, add, or confirm auto-proposed decisions. Also supports deprecation and dismissal.
/adrInteractively creates Architecture Decision Records (ADRs) through guided conversation, documenting context, options, rationale per template, and updates architecture overview.
/generateGenerates final ADR document from prior analysis: prompts for decision details, analyzes consequences, writes MADR-formatted file to docs/adr/ or specified path, cleans session.
Share bugs, ideas, or general feedback.
Launches the adr-analyzer agent to identify potential ADRs in specified modules.
When multiple modules are specified, launches agents in parallel for faster analysis.
Prerequisites: Run /adr-map first if mapping.md doesn't exist in the output directory.
What it does:
Usage:
/adr-identify [module-ids] [--output-dir=PATH] [--adrs-dir=PATH]
Examples:
/adr-identify
# Prompts which modules to analyze (uses docs/adrs by default)
/adr-identify AUTH
# Analyze only AUTH module
/adr-identify AUTH DATA API
# Analyze multiple modules
/adr-identify --output-dir=output/adrs AUTH
# Analyze AUTH module with custom output directory
/adr-identify --adrs-dir=docs/adrs/generated AUTH
# Uses existing ADRs from custom directory for context and duplicate detection
Output Structure:
{OUTPUT_DIR}/potential-adrs/ # Default: docs/adrs/potential-adrs
├── must-document/ # High priority (score ≥100 out of 150)
│ └── MODULE-ID/
│ ├── decision-title-kebab-case.md
│ └── another-architectural-decision.md
└── consider/ # Medium priority (score 75-99 out of 150)
└── MODULE-ID/
└── medium-priority-decision.md
Important: Filenames use descriptive kebab-case WITHOUT numbers. Numbering happens in Phase 3 when formal ADRs are generated.
Existing ADR Integration: Automatically scans {OUTPUT_DIR}/generated/ (or --adrs-dir path) for existing ADRs to:
How It Works:
Key Features:
Expected Results:
Note: This identifies potential ADRs with evidence. You decide which to formally document in Phase 3.
When the user invokes /adr-identify with module IDs:
Extract from command:
--output-dir=<path>: Optional output directory (default: docs/adrs)--adrs-dir=<path>: Optional existing ADRs directory (default: {OUTPUT_DIR}/generated/)/adr-identify AUTH)Launch a single adr-analyzer agent with the Task tool:
Without --output-dir:
Task tool:
- subagent_type: adr-analyzer
- prompt: "Identify potential ADRs for the AUTH module"
With --output-dir:
Task tool:
- subagent_type: adr-analyzer
- prompt: "Identify potential ADRs for the AUTH module with --output-dir=custom/path"
With --adrs-dir:
Task tool:
- subagent_type: adr-analyzer
- prompt: "Identify potential ADRs for the AUTH module with --adrs-dir=docs/adrs/generated"
/adr-identify AUTH DATA API or /adr-identify --output-dir=output/adrs AUTH DATA)Launch multiple adr-analyzer agents in parallel using a single message with multiple Task tool calls:
Without --output-dir:
Single message with multiple Task tool calls:
Task tool call 1:
- subagent_type: adr-analyzer
- prompt: "Identify potential ADRs for the AUTH module"
Task tool call 2:
- subagent_type: adr-analyzer
- prompt: "Identify potential ADRs for the DATA module"
Task tool call 3:
- subagent_type: adr-analyzer
- prompt: "Identify potential ADRs for the API module"
With --output-dir:
Single message with multiple Task tool calls:
Task tool call 1:
- subagent_type: adr-analyzer
- prompt: "Identify potential ADRs for the AUTH module with --output-dir=custom/path"
Task tool call 2:
- subagent_type: adr-analyzer
- prompt: "Identify potential ADRs for the DATA module with --output-dir=custom/path"
Task tool call 3:
- subagent_type: adr-analyzer
- prompt: "Identify potential ADRs for the API module with --output-dir=custom/path"
IMPORTANT:
/adr-identify or /adr-identify --output-dir=custom/path)docs/adrs){OUTPUT_DIR}/mapping.md to get available modules