quaestor 0.6.3

AI-assisted development context management tool for maintaining consistency and productivity

Quaestor

🏛️ Context management for AI-assisted development

Quaestor transforms AI-assisted development through specification-driven workflows, intelligent agent orchestration, and streamlined context management for Claude Code.

Key Features

• 🎯 Specification-Driven Development - Clear contracts with acceptance criteria and lifecycle management
• 🤖 13 Specialized AI Agents - Expert agents including new speccer for YAML generation
• 🔄 Smart Automation Hooks - Automatic spec validation and progress tracking
• ⚡ 40% Faster Context Loading - Consolidated templates for better performance
• ✅ Specification Validation - Built-in quaestor validate command for spec files

Quick Start

Using uvx (Recommended - No Installation Required)

# Initialize Quaestor without installing it
uvx quaestor init

# Team mode - shared configuration
uvx quaestor init --mode team

# Update to latest version
uvx quaestor update

Traditional Installation

# Install globally
pip install quaestor

# Initialize project
quaestor init

# Create your first specification
/plan "User Authentication System"

# Implement the specification
/impl spec-auth-001

Project Modes

Personal Mode (Default)

Perfect for individual projects:

quaestor init

• Commands installed globally in ~/.claude/commands/
• Local settings in .claude/settings.local.json (not committed)
• Project files in .quaestor/ (gitignored)
• CLAUDE.md with project-specific context

Team Mode

For shared projects with consistent standards:

quaestor init --mode team

• Commands in .claude/commands/ (committed, shared with team)
• Settings in .claude/settings.json (committed)
• Project files in .quaestor/ (committed)
• CLAUDE.md with team standards and context

Key Difference: Personal mode keeps configuration local, Team mode shares everything with the team.

Core Commands

• /plan "Feature Name" - Create specification with clear contracts
• /impl spec-id - Implement according to specification
• /research "topic" - Analyze codebase patterns and architecture
• /review spec-id - Validate implementation quality
• /debug "issue" - Systematic debugging and fixes
• quaestor validate spec.yaml - Validate specification file structure

How It Works

Specification-First Development

1. Plan with Contracts - /plan creates detailed specifications with input/output contracts
2. Lifecycle Management - Specs move through draft/ → active/ → completed/ folders
3. Agent Orchestration - 13 specialized agents collaborate on implementation
4. Quality Assurance - Built-in testing and review workflows with automatic validation

Example Workflow

# 1. Create specification
/plan "JWT Authentication API"
# → Creates spec-auth-001.yaml in draft/ folder

# 2. Implement with guided workflow
/impl spec-auth-001  
# → Moves to active/, orchestrates architect → implementer → qa agents

# 3. Review and deploy
/review spec-auth-001
# → Validates quality, moves to completed/ when done

Hook System

Quaestor's hooks integrate seamlessly with Claude Code using uvx, requiring no local installation:

• Session Context Loader - Automatically loads active specifications at session start
• Progress Tracker - Updates specification progress when TODOs are completed
• Spec Validator - Validates specification YAML files on save (blocks on errors)
• No Python Required - Hooks run via uvx without installing Quaestor in your project

The hooks are configured in .claude/settings.json and execute Quaestor commands remotely via uvx.

Documentation

📚 Full Documentation

• Installation & Setup
• Quick Start Guide
• Specification-Driven Development
• Agent System

Contributing

git clone https://github.com/jeanluciano/quaestor.git
cd quaestor
pip install -e .
pytest

License

MIT License

---

Documentation · Issues