claude-gen

Claude Gen Plugin

Generate project structure, documentation (BRD/PRD/SRS/UI Mockup), and code from a requirements file.

Installation

Via Marketplace

# Add the marketplace
/plugin marketplace add tductam/code-gen

# Install the plugin
/plugin install claude-gen@claude-gen-marketplace

Via GitHub

/plugin marketplace add https://github.com/tductam/code-gen.git
/plugin install claude-gen@claude-gen-marketplace

Via Local Path (for development)

claude --plugin-dir ./path-to/code-gen

Usage

Full Pipeline

/claude-gen:generate <path-to-requirements-file>

Incremental (run individual phases)

/claude-gen:generate requirements.md --phase init    # Phase 1: Analyze/Init only
/claude-gen:generate requirements.md --phase docs    # Phase 2: Gen docs only
/claude-gen:generate requirements.md --phase code    # Phase 3: Gen code only

Examples

/claude-gen:generate requirements.md
/claude-gen:generate docs/feature-request.md
/claude-gen:generate requirements.md --phase docs

Pipeline

requirements.md → [init-explorer] → [gen-doc] → [gen-code] → Done

Phase	Agent	Description
1	init-explorer	Analyze existing codebase or scaffold new project
2	gen-doc	Generate BRD, PRD, SRS, UI Mockups, API Contracts
3	gen-code	Generate implementation code following conventions

Output

All intermediate artifacts are saved to .generated/:

.generated/
├── analysis/              # Phase 1 output
│   ├── project-overview.md
│   ├── frontend-structure.md
│   ├── backend-structure.md
│   ├── tech-stack.md
│   ├── conventions.md
│   └── manifest.json
├── docs/                  # Phase 2 output
│   ├── BRD.md             # Business Requirements Document
│   ├── PRD.md             # Product Requirements Document
│   ├── SRS.md             # Software Requirements Specification
│   ├── manifest.json
│   ├── api-contracts/
│   │   └── <module>.md
│   └── ui-mockups/
│       └── screen-<name>.md
├── code/                  # Phase 3 metadata
│   └── manifest.json
└── dependencies.json      # Dependencies to install

Phase 3 writes code directly into the project source tree.

Safety Features

• Validation: Each agent produces a manifest.json — the next agent checks it before running
• Rollback: Git checkpoint (stash) created before each phase — auto-rollback on failure
• Non-destructive: Existing files are NOT overwritten without user confirmation
• Cross-platform: Supports Windows (PowerShell) and Unix/Linux/macOS (Bash)
• Dependencies Tracking: Tracks and reports all dependencies that need to be installed

Requirements File Format

# Project Name

## Description
Brief project description.

## Business Context (optional - for BRD)
- **Business Problem**: Problem to solve
- **Target Users**: User personas
- **Business Goals**: Objectives with metrics

## Features
- Feature 1: detailed description
- Feature 2: detailed description

## Tech Stack (optional)
- Frontend: React / Next.js / Vue...
- Backend: NestJS / Express / FastAPI...
- Database: PostgreSQL / MongoDB...

## Screens (optional - for FE)
- Login: Screen description
- Dashboard: Screen description
- Settings: Screen description

## API Modules (optional - for BE)
- Auth: Module description
- Users: Module description
- Products: Module description

## Non-Functional Requirements (optional)
- Performance targets
- Security requirements
- Scalability needs
- Accessibility standards

## Out of Scope (optional)
- Features not included in this version

Example: See examples/requirements.md for a complete example.

Generated Documents

BRD (Business Requirements Document)

• Executive summary & business vision
• Business objectives with target metrics
• Stakeholder analysis
• Market analysis & competitive landscape
• Detailed user personas
• Business requirements (BR-001, BR-002, ...)
• Financial analysis & ROI
• Risks and mitigation strategies
• Implementation timeline with Gantt chart

PRD (Product Requirements Document)

• Product overview & success metrics
• User stories (US-001, US-002, ...) with acceptance criteria
• Feature requirements by module
• Non-functional requirements
• Out of scope items
• Phased delivery timeline
• Cross-references to BRD

SRS (Software Requirements Specification)

• System architecture diagram
• Frontend specification (tech stack, screens, components)
• Backend specification (tech stack, API endpoints, database)
• Data flow diagrams
• Error handling strategy
• Security specification with auth flows

UI Mockups (Per Screen)

• Screen flow diagram
• Component tree visualization
• Desktop/Tablet/Mobile layouts (ASCII wireframes)
• Component specifications table
• State management design
• API calls per screen
• User interaction flows