██████╗ ██████╗ ██████╗ ███╗ ███╗███████╗████████╗██╗ ██╗
██╔══██╗██╔══██╗██╔═══██╗████╗ ████║██╔════╝╚══██╔══╝██║ ██║
██████╔╝██████╔╝██║ ██║██╔████╔██║█████╗ ██║ ███████║
██╔═══╝ ██╔══██╗██║ ██║██║╚██╔╝██║██╔══╝ ██║ ██╔══██║
██║ ██║ ██║╚██████╔╝██║ ╚═╝ ██║███████╗ ██║ ██║ ██║
╚═╝ ╚═╝ ╚═╝ ╚═════╝ ╚═╝ ╚═╝╚══════╝ ╚═╝ ╚═╝ ╚═╝
CONTEXT FRAMEWORK
"Just as Prometheus gave humanity fire, this framework gives AI users the tools to ignite high-quality, predictable output."
A comprehensive AI tooling framework that provides structured commands and templates for creating strategic Product Requirements Documents (PRDs), implementation Specifications (SPECs), and technical documentation. Designed to deliver predictable, high-quality output for software development teams.
- End-to-End Lifecycle: From strategic vision to guided delivery
- 6 Unified Commands: Streamlined workflow with comprehensive tracking
- CLAUDE.md Validation: Mandatory project configuration ensures proper context
- Smart Input Handling: Supports file paths, text input, and interactive prompts
- Epic-Level Documentation: Comprehensive PRDs for cross-functional initiatives
- Market Analysis Integration: Built-in templates for competitive positioning and business justification
- Stakeholder Alignment: Structured formats for quarterly planning and strategic decisions
- Scope Validation: Automatic detection of strategic vs. tactical content
- 3-Phase Workflow: Structured Planning → Task Breakdown → Implementation phases
- Guided Implementation: Interactive execution with progress tracking (
/prometh-build) - User Story Documentation: Task-level specifications ready for development teams
- Auto-Classification: Automatic categorization as Feature/Bug Fix/Enhancement/Task
- Comprehensive Testing: Built-in test strategies and acceptance criteria
- Complete Traceability: Full visibility from strategic vision to delivery
- Repository Analysis: Smart analysis to determine appropriate documentation style
- Unified Templates: Single template per documentation type for consistency
- Multi-Format Support: README and runbook generation with auto-detection
-
Clone the repository:
git clone https://github.com/ivannagy/prometh-context-framework.git cd prometh-context-framework -
Run the setup script:
./setup.sh
-
Verify installation:
# Check installed commands in Claude Code ls ~/.claude/commands/prometh-*
After installing the framework commands, initialize it in any project:
-
Initialize Claude Code in your project:
# Navigate to your project directory cd /path/to/your/project # Initialize with Claude Code (creates CLAUDE.md) /init
-
Initialize Prometh Framework:
# Set up Prometh tracking and directory structure /prometh-init -
Verify setup:
# Check created directories and tracking file ls docs/prds docs/specs ls PROMETH.md
# Interactive mode - prompts for strategic description
/prometh-prd
# Create from file - normalizes existing strategic documents
/prometh-prd strategic-planning-document.pdf
# Text input mode - provide content directly in prompt
/prometh-prd
# Then paste or type your strategic initiative description# Interactive mode - prompts for implementation description
/prometh-spec
# Create from user story file
/prometh-spec user-story.md
# Convert bug report to SPEC format
/prometh-spec bug-report.pdf# Generate comprehensive README
/prometh-doc readme
# Create operational runbook
/prometh-doc runbook# Execute SPEC with guided workflow
/prometh-build docs/specs/user-authentication-spec.md
# Resume implementation from last checkpoint
/prometh-build docs/specs/payment-integration-spec.md# Full project status overview
/prometh-status
# Quick summary view
/prometh-status --brief
# Health metrics and suggestions
/prometh-status --healthprometh-context-framework/
├── .claude/
│ ├── commands/ # 6 unified Claude Code commands
│ │ ├── prometh-init.md # Framework initialization and project setup
│ │ ├── prometh-prd.md # Strategic PRD creation & normalization
│ │ ├── prometh-spec.md # Implementation SPEC creation & normalization
│ │ ├── prometh-build.md # Guided SPEC implementation execution
│ │ ├── prometh-doc.md # Technical documentation generation
│ │ ├── prometh-status.md # Project documentation status dashboard
│ │ └── prometh-help.md # Comprehensive command reference
│ └── output-styles/ # 4 unified templates
│ ├── prometh-prd.md # Unified PRD template
│ ├── prometh-spec.md # Unified SPEC template with workflow
│ ├── prometh-doc-readme.md # Unified README template
│ └── prometh-doc-runbook.md # Specialized runbook template
├── docs/ # Created by /prometh-init
│ ├── prds/ # Strategic Product Requirements Documents
│ └── specs/ # Implementation Specifications
├── setup.sh # Installation script
├── CLAUDE.md # Claude Code configuration
├── PROMETH.md # Framework status and document tracking (created by /prometh-init)
└── LICENSE # Apache License 2.0
| Command | Purpose | Input Types | Output Location |
|---|---|---|---|
/prometh-init |
Initialize framework in project | N/A | Current directory |
/prometh-prd |
Create or normalize strategic PRDs | Descriptions, file paths, interactive | docs/prds/ |
/prometh-spec |
Create or normalize implementation SPECs | User stories, bug reports, file paths, interactive, PRD references | docs/specs/ |
/prometh-build |
Execute SPEC with guided implementation | SPEC file path (required) | PROMETH.md tracking |
/prometh-doc |
Generate technical documentation | readme or runbook types |
Current directory |
/prometh-status |
Display project documentation status dashboard | Optional flags: --brief, --counts, --health |
Console output |
/prometh-help |
Display comprehensive command reference | N/A | Console output |
The framework uses 4 simplified templates (reduced from 11):
- prometh-prd: Unified PRD template handling all strategic scenarios
- Quarterly planning and roadmap initiatives
- Market positioning and competitive strategy
- Cross-functional initiatives and major feature launches
- prometh-spec: Unified SPEC template with 3-phase workflow
- Phase 1: Planning - Requirements analysis, technical design, resource planning
- Phase 2: Task Breakdown - Development tasks, acceptance criteria, dependencies
- Phase 3: Implementation - Execution, testing, deployment, validation
- prometh-doc-readme: Comprehensive README template for project documentation
- prometh-doc-runbook: Specialized template for operational procedures and troubleshooting
All commands require CLAUDE.md or CLAUDE.local.md in the project root:
- Context Assurance: Ensures proper project configuration
- Clear Error Handling: Guides users to create required configuration files
- Consistent Behavior: Standardized validation across all commands
- PRD vs SPEC Detection: Automatic classification based on strategic vs. tactical content
- Implementation Type Detection: Auto-categorizes SPECs as Feature/Bug Fix/Enhancement/Task
- Scope Validation: Prevents misclassification and suggests appropriate commands
# Epic-level initiative
/prometh-prd
# Prompt: "Implement microservices architecture migration for improved scalability and team autonomy"
# Output: docs/prds/microservices-architecture-migration-prd.md# Normalize strategic document from file
/prometh-prd quarterly-planning-doc.pdf
# Output: docs/prds/quarterly-planning-initiative-prd.md
# Normalize implementation requirements
/prometh-spec feature-requirements.md
# Output: docs/specs/feature-user-authentication-spec.md# Auto-detect project type and generate README
/prometh-doc readme
# Analyzes repository structure and creates comprehensive README.md
# Generate operational runbook
/prometh-doc runbook
# Creates runbook based on system configuration analysisYour complete workflow is now:
/prometh-prd → /prometh-spec → /prometh-build → Delivery
Strategic Implementation Guided Complete
Vision Planning Execution Traceability
- Create strategic PRDs for Epic-level initiatives
- Market analysis and business justification
- Cross-functional alignment and stakeholder buy-in
- Convert PRDs into actionable SPECs
- 3-phase workflow structure (Planning → Task Breakdown → Implementation)
- Detailed acceptance criteria and technical requirements
- Interactive implementation tracking through SPEC phases
- Real-time progress updates in PROMETH.md
- Phase transition validation and milestone tracking
- Complete traceability from strategic vision to delivery
When using /prometh-build, you'll be guided through:
- Requirements analysis and clarification
- Technical design and architecture decisions
- Resource allocation and timeline estimation
- Deliverable validation and sign-off
- Create detailed development tasks with priorities
- Define acceptance criteria for each task
- Identify dependencies and critical path
- Risk assessment and mitigation planning
- Execute development tasks in priority order
- Perform integration testing and quality assurance
- Deploy to staging and production environments
- Validate against original SPEC acceptance criteria
Initialize your project with Claude Code to create the required configuration:
# Initialize project with Claude Code (creates CLAUDE.md)
/init
# Or create local override file manually if needed
touch CLAUDE.local.mdThe framework automatically creates required directories:
docs/prds/- Strategic Product Requirements Documentsdocs/specs/- Implementation Specifications
- Fork the repository
- Create your feature branch:
git checkout -b feature/amazing-feature - Test your changes with the setup script
- Commit your changes:
git commit -m 'Add amazing feature' - Push to the branch:
git push origin feature/amazing-feature - Open a Pull Request
- Follow the unified command structure in
.claude/commands/ - Test output styles thoroughly before submitting
- Update documentation for new features
- Maintain backward compatibility with existing functionality
This project is licensed under the Apache License 2.0 - see the LICENSE file for details.
The Prometh Context Framework follows a dual-documentation approach:
- PRDs (Strategic): For Epic-level initiatives requiring cross-functional alignment, market analysis, and business justification
- SPECs (Implementation): For User Story/Task-level documentation that development teams can execute directly with structured 3-phase workflow
This separation ensures that strategic planning remains focused on business value while implementation details stay practical and actionable.
- 6 Commands: End-to-end lifecycle from strategic planning to guided delivery
- Interactive Execution:
/prometh-buildprovides guided implementation with progress tracking - Unified Templates: Single template per command type reduces complexity
- Smart Input: Handles files, text, and interactive input seamlessly
- Status Dashboard: Real-time visibility into documentation health and progress
- Guided Implementation: Interactive execution with
/prometh-buildfor SPECs - 3-Phase Workflow: Structured implementation approach with progress tracking
- Auto-Classification: Prevents document type confusion
- Complete Traceability: Full visibility from strategic PRDs through SPEC execution to delivery
- Unified Templates: Predictable structure across all document types
- Professional Standards: Enterprise-ready documentation formatting
- Attribution Included: All documents credit the Prometh Context Framework
- Claude Code - Official Claude CLI tool
- Claude API - Anthropic's Claude API documentation
Ready to ignite high-quality, predictable output! 🔥