Help us improve
Share bugs, ideas, or general feedback.
Share bugs, ideas, or general feedback.
Share bugs, ideas, or general feedback.
By devfullcycle
Map codebase into modules, discover potential Architecture Decision Records (ADRs) from git history and structure, generate formal MADR-compliant ADRs, detect relationships like supersedes or amends, and create bidirectional clickable Markdown links for navigation and validation.
npx claudepluginhub devfullcycle/claude-mkt-place --plugin adrs-managementGenerate formal ADRs from potential ADRs
Identify potential ADRs for specific modules based on the codebase mapping (Phase 2)
Detect and create bidirectional relationships between existing ADRs with clickable links
Create a modular codebase mapping to prepare for ADR identification (Phase 1)
Use this agent when you need to analyze a codebase to understand its architecture and generate Architecture Decision Records (ADRs). This is a two-phase process: Phase 1 - Codebase Mapping: <example> Context: User wants to start analyzing their codebase for ADR generation. user: "I need to understand the architecture of this project and create ADRs for it" assistant: "I'll use the adr-analyzer agent to begin the codebase mapping phase, which will analyze the project structure and create the initial mapping document." <Task tool call to adr-analyzer agent> </example> <example> Context: User has a large legacy codebase without documentation. user: "Can you help me document the architectural decisions in this codebase?" assistant: "Let me use the adr-analyzer agent to first map out the codebase structure and identify the technologies and architectural patterns used." <Task tool call to adr-analyzer agent> </example> Phase 2 - ADR Identification: <example> Context: The mapping.md file has been created with modular structure and user wants to proceed with ADR identification. user: "The mapping is complete, now identify potential ADRs for the AUTH and API modules" assistant: "I'll use the adr-analyzer agent to analyze the AUTH and API modules from the mapping and identify potential ADRs for these specific areas." <Task tool call to adr-analyzer agent> </example> <example> Context: User has a large codebase (5000+ files) and wants to analyze incrementally. user: "Start identifying ADRs, but do it module by module to avoid overwhelming the context" assistant: "I'll use the adr-analyzer agent to read the mapping and present the available modules, then we can analyze them systematically one or two at a time." <Task tool call to adr-analyzer agent> </example> <example> Context: User wants to continue ADR analysis from where they left off. user: "Continue the ADR analysis. We already did AUTH and API, let's do DATA and PAYMENT next" assistant: "I'll use the adr-analyzer agent to analyze the DATA and PAYMENT modules and append the findings to the existing potential_adrs.md." <Task tool call to adr-analyzer agent> </example> <example> Context: User is working on improving project documentation after initial development. user: "We've built this system over the past year but never documented our architectural decisions. Can you help?" assistant: "I'll use the adr-analyzer agent to analyze your codebase systematically. We'll start with mapping the architecture into logical modules, then identify key decisions module by module to keep analysis manageable." <Task tool call to adr-analyzer agent> </example>
Generate a formal ADR from a single potential ADR file identified in the codebase. This agent processes ONE file at a time. When multiple files need processing, the command launcher invokes multiple instances of this agent in parallel.
Detect and create bidirectional relationships between existing ADRs with clickable Markdown links. Analyzes temporal evolution, technical dependencies, semantic similarity, and explicit hints to build a comprehensive ADR relationship graph.
Uses power tools
Uses Bash, Write, or Edit tools
Share bugs, ideas, or general feedback.
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge.
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge.
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Project Analyzer plugins for comprehensive architectural analysis, component deep analysis, and dependency auditing
Architecture Decision Records authoring and management
Human-in-the-loop Architecture Decision Record workflow
AI-powered architecture documentation framework with ADRs, reviews, and pragmatic mode
Make your AI agent code with your project's architecture, rules, and decisions.
Documentation generation with API docs, architecture diagrams, and tutorials
Project Analyzer plugins for comprehensive architectural analysis, component deep analysis, and dependency auditing
Diagrams Generator plugins for C4 and Mermaid diagram generation from Feature Design Documents
Development Guidelines plugin for generating comprehensive language-specific development guideline documents
A collection of Claude Code plugins for software architecture and design documentation.
This marketplace provides four powerful plugins for architectural documentation and analysis:
To use these plugins, first add this marketplace to Claude Code:
/plugin marketplace add devfullcycle/claude-mkt-place
This command adds the GitHub repository as a plugin marketplace source.
After adding the marketplace, install individual plugins:
# Install ADRs Management plugin
/plugin install adrs-management@devfullcycle
# Install Diagrams Generator plugin
/plugin install diagrams-generator@devfullcycle
# Install Project Analyzer plugin
/plugin install project-analizer@devfullcycle
# Install Development Guidelines plugin
/plugin install development-guidelines@devfullcycle
Note: The marketplace identifier (devfullcycle) is derived from the GitHub organization/username. After adding the marketplace, you can also browse available plugins using:
/plugin
Document architectural decisions systematically:
/adr-map # Phase 1: Map codebase
/adr-identify AUTH DATA # Phase 2: Identify potential ADRs
/adr-generate BILLING # Phase 3: Generate formal ADRs
/adr-link # Link ADRs with relationships
Create visual documentation from FDDs:
/c4-generate docs/features/payment-fdd.md
/mermaid-generate docs/features/auth-fdd.md
Analyze project architecture and dependencies:
/generate-architectural-report
/run-dependency-audit
Generate comprehensive development guidelines for any programming language:
/generate-development-guideline Python
/generate-development-guideline TypeScript --orm=prisma --web=express --testing=jest
/generate-development-guideline Go --orm=sqlc --web=chi --db=pgx
For detailed usage instructions, see each plugin's documentation: