@hivehub/rulebook 1.2.0

package/templates/cli/AIDER.md

@@ -0,0 +1,49 @@
+<!-- AIDER:START -->
+# Aider CLI Rules
+
+**Tool**: AI pair programming in terminal (`pip install aider-chat`)
+
+## Quick Start
+
+```bash
+# Always include AGENTS.md
+aider AGENTS.md src/feature.ts tests/feature.test.ts
+
+# In chat:
+"Follow AGENTS.md standards. Implement [feature] with tests first."
+```
+
+## Essential Commands
+
+```bash
+/add file.ts          # Add files to context
+/drop file.ts         # Remove from context
+/run npm test         # Run command
+/commit "message"     # Commit changes
+/undo                 # Undo last change
+/diff                 # Review changes
+```
+
+## Configuration (.aider.conf.yml)
+
+```yaml
+model: gpt-4
+read: [AGENTS.md]
+lint: true
+lint-cmd: "npm run lint"
+test-cmd: "npm test"
+auto-commits: true
+commit-prompt: true
+```
+
+## Workflow
+
+1. Start session with `aider AGENTS.md [files]`
+2. Request: "Follow AGENTS.md. Implement [feature] with tests first (95%+ coverage)"
+3. Review diffs with `/diff`
+4. Test with `/run npm test`
+5. Commit with `/commit "feat: description"`
+
+**Critical**: Always reference AGENTS.md in your requests for consistent standards.
+
+<!-- AIDER:END -->

package/templates/cli/AMAZON_Q.md

@@ -0,0 +1,25 @@
+<!-- AMAZON_Q:START -->
+# Amazon Q Developer Rules
+
+**Tool**: AWS-focused AI assistant with security scanning
+
+## Quick Start
+
+Available in AWS IDE Toolkit or via AWS Console.
+
+## Usage
+
+```
+"Follow @AGENTS.md standards. Implement [feature] with tests (95%+ coverage)."
+```
+
+## Workflow
+
+1. Reference AGENTS.md in prompts
+2. Leverage Q's security scanning for vulnerabilities
+3. Review generated code
+4. Run quality checks
+
+**Critical**: Q excels at AWS/security - combine with AGENTS.md standards.
+
+<!-- AMAZON_Q:END -->

package/templates/cli/AUGGIE.md

@@ -0,0 +1,32 @@
+<!-- AUGGIE:START -->
+# Auggie (Augment CLI) Rules
+
+**Tool**: TDD mode and intelligent refactoring
+
+## Quick Start
+
+```bash
+npm install -g augment-cli
+augment --tdd
+```
+
+## Usage
+
+```bash
+# TDD mode with AGENTS.md:
+augment --tdd --context AGENTS.md
+
+# In prompts:
+"Follow @AGENTS.md. Write tests for [feature], then implement."
+```
+
+## Workflow
+
+1. Use `--tdd` flag for test-first development
+2. Include `--context AGENTS.md`
+3. Auggie writes tests, then implementation
+4. Review and verify coverage
+
+**Critical**: TDD mode aligns perfectly with AGENTS.md test-first approach.
+
+<!-- AUGGIE:END -->

package/templates/cli/CLAUDE.md

@@ -0,0 +1,32 @@
+<!-- CLAUDE:START -->
+# Claude API/CLI Rules
+
+**Tool**: Anthropic Claude API with 200K context window
+
+## Quick Start
+
+```bash
+export ANTHROPIC_API_KEY=your_key
+# Use via API or compatible CLIs
+```
+
+## Usage
+
+In API requests or CLI prompts, include:
+```
+"Follow these project standards from AGENTS.md:
+[paste relevant AGENTS.md sections]
+
+Implement [feature] with tests first (95%+ coverage)."
+```
+
+## Workflow
+
+1. Include AGENTS.md content in system prompt or context
+2. Request features with standards reference
+3. Review generated code
+4. Run quality checks
+
+**Critical**: Claude has 200K context - paste full AGENTS.md for best results.
+
+<!-- CLAUDE:END -->

package/templates/cli/CLAUDE_CODE.md

@@ -0,0 +1,35 @@
+<!-- CLAUDE_CODE:START -->
+# Claude Code CLI Rules
+
+**Tool**: Anthropic Claude coding assistant (`npm install -g @anthropic-ai/claude-code`)
+
+## Quick Start
+
+```bash
+export ANTHROPIC_API_KEY=your_key
+claude-code --model claude-3-5-sonnet --files AGENTS.md
+```
+
+## Essential Usage
+
+```bash
+# Load AGENTS.md for standards
+claude-code --files AGENTS.md --task "Implement [feature] following AGENTS.md with tests"
+
+# Key flags:
+--model claude-3-5-sonnet    # Model selection
+--files AGENTS.md            # Include standards
+--stream                     # Real-time output
+--verbose                    # Debug mode
+```
+
+## Workflow
+
+1. Always include `--files AGENTS.md` for project standards
+2. Request: "Follow AGENTS.md. Implement [feature] with tests (95%+ coverage)"
+3. Review generated code
+4. Run quality checks: `npm run lint && npm test`
+
+**Critical**: Reference AGENTS.md in prompts for consistent code generation.
+
+<!-- CLAUDE_CODE:END -->

package/templates/cli/CLINE.md

@@ -0,0 +1,32 @@
+<!-- CLINE:START -->
+# Cline CLI Rules
+
+**Tool**: VS Code extension with autonomous mode
+
+## Quick Start
+
+Install Cline extension in VS Code or use CLI mode.
+
+## Usage
+
+```bash
+# In prompts, always reference standards:
+"Follow @AGENTS.md. Implement [feature] with tests first (95%+ coverage)."
+
+# Cline will:
+- Read AGENTS.md
+- Write tests
+- Implement feature
+- Run quality checks
+```
+
+## Workflow
+
+1. Keep AGENTS.md open in workspace
+2. Request features with "Follow @AGENTS.md" prefix
+3. Review proposed changes before approval
+4. Verify tests pass after implementation
+
+**Critical**: Reference @AGENTS.md in every prompt for consistent output.
+
+<!-- CLINE:END -->

package/templates/cli/CODEBUDDY.md

@@ -0,0 +1,20 @@
+<!-- CODEBUDDY:START -->
+# CodeBuddy Code Rules
+
+**Tool**: Intelligent pair programming assistant
+
+## Usage
+
+Reference AGENTS.md in all requests:
+```
+"Follow @AGENTS.md standards. Implement [feature] with tests first."
+```
+
+## Workflow
+
+1. Include AGENTS.md in context
+2. Request features with standards reference
+3. Review code
+4. Run `npm run lint && npm test`
+
+<!-- CODEBUDDY:END -->

package/templates/cli/CODEIUM.md

@@ -0,0 +1,20 @@
+<!-- CODEIUM:START -->
+# Codeium CLI/Extension Rules
+
+**Tool**: Free AI coding assistant
+
+## Usage
+
+Reference AGENTS.md in prompts:
+```
+"Follow @AGENTS.md. Implement [feature] with tests (95%+ coverage)."
+```
+
+## Workflow
+
+1. Keep AGENTS.md open for context
+2. Use inline suggestions or chat
+3. Review generated code
+4. Run quality checks
+
+<!-- CODEIUM:END -->

package/templates/cli/CODEX.md

@@ -0,0 +1,21 @@
+<!-- CODEX:START -->
+# Codex (OpenAI) Rules
+
+**Tool**: OpenAI code generation API
+
+## Usage
+
+Include AGENTS.md content in API system prompt:
+```
+System: "Follow these standards: [AGENTS.md content]"
+User: "Implement [feature] with tests (95%+ coverage)."
+```
+
+## Workflow
+
+1. Paste AGENTS.md into system prompt
+2. Request features
+3. Review code
+4. Run quality checks
+
+<!-- CODEX:END -->

package/templates/cli/CONTINUE.md

@@ -0,0 +1,34 @@
+<!-- CONTINUE:START -->
+# Continue CLI/Extension Rules
+
+**Tool**: Open-source Copilot alternative (VS Code extension + CLI)
+
+## Quick Start
+
+```bash
+# In VS Code: Install Continue extension
+# Or CLI: npm install -g continue-cli
+```
+
+## Usage
+
+```bash
+# Always reference AGENTS.md in prompts:
+"Follow @AGENTS.md standards. Implement [feature] with tests (95%+ coverage)."
+
+# Slash commands:
+/edit    # Edit files
+/chat    # Ask questions
+/cmd     # Run terminal commands
+```
+
+## Workflow
+
+1. Open AGENTS.md in editor for Continue to read
+2. Use `/edit` to modify code following standards
+3. Reference AGENTS.md in every request
+4. Run quality checks after changes
+
+**Critical**: Keep AGENTS.md open or reference it explicitly in prompts.
+
+<!-- CONTINUE:END -->

package/templates/cli/CURSOR_CLI.md

@@ -0,0 +1,28 @@
+<!-- CURSOR_CLI:START -->
+# Cursor CLI Rules
+
+**Tool**: Cursor IDE automation and scripting
+
+## Quick Start
+
+```bash
+# Cursor reads .cursorrules automatically
+# This file is generated by rulebook init
+```
+
+## Usage
+
+Cursor automatically references:
+- `.cursorrules` (generated by rulebook)
+- `AGENTS.md` (via @AGENTS.md references)
+
+## Workflow
+
+1. Use `@AGENTS.md` in chat to reference standards
+2. Request: "Follow @AGENTS.md. Implement [feature] with tests."
+3. Cursor respects .cursorrules and AGENTS.md automatically
+4. Review and accept changes
+
+**Critical**: Generated `.cursorrules` points to AGENTS.md. Use @ mentions for explicit references.
+
+<!-- CURSOR_CLI:END -->

package/templates/cli/FACTORY.md

@@ -0,0 +1,18 @@
+<!-- FACTORY:START -->
+# Factory Droid Rules
+
+**Tool**: Code generation and automation
+
+## Usage
+
+```
+"Follow @AGENTS.md standards. Generate [code] with tests."
+```
+
+## Workflow
+
+1. Reference AGENTS.md in prompts
+2. Review generated code
+3. Run quality checks
+
+<!-- FACTORY:END -->

package/templates/cli/GEMINI.md

@@ -0,0 +1,35 @@
+<!-- GEMINI:START -->
+# Gemini CLI Rules
+
+**Tool**: Google Gemini API with 2M token context
+
+## Quick Start
+
+```bash
+# Install gemini CLI
+npm install -g @google/generative-ai-cli
+
+# Set API key
+export GEMINI_API_KEY=your_key
+```
+
+## Usage
+
+```bash
+# Always reference AGENTS.md:
+gemini --prompt "Read @AGENTS.md. Implement [feature] with tests (95%+ coverage)."
+
+# Include files:
+gemini --files AGENTS.md,src/feature.ts
+```
+
+## Workflow
+
+1. Include AGENTS.md in context with `--files AGENTS.md`
+2. Request: "Follow @AGENTS.md. Implement [feature] with tests."
+3. Review output
+4. Run quality checks: `npm run lint && npm test`
+
+**Critical**: Reference @AGENTS.md for consistent code generation.
+
+<!-- GEMINI:END -->

package/templates/cli/KILOCODE.md

@@ -0,0 +1,18 @@
+<!-- KILOCODE:START -->
+# Kilo Code Rules
+
+**Tool**: Lightweight coding companion
+
+## Usage
+
+```
+"Follow @AGENTS.md. Implement [feature] with tests."
+```
+
+## Workflow
+
+1. Reference AGENTS.md
+2. Review code
+3. Run quality checks
+
+<!-- KILOCODE:END -->

package/templates/cli/OPENCODE.md

@@ -0,0 +1,18 @@
+<!-- OPENCODE:START -->
+# OpenCode Rules
+
+**Tool**: Open-source AI assistant
+
+## Usage
+
+```
+"Follow @AGENTS.md. Implement [feature] with tests."
+```
+
+## Workflow
+
+1. Reference AGENTS.md
+2. Review code
+3. Run quality checks
+
+<!-- OPENCODE:END -->

package/templates/cli/_GENERIC_TEMPLATE.md

@@ -0,0 +1,29 @@
+<!-- {TOOL}:START -->
+# {Tool Name} CLI Rules
+
+**Tool**: {Brief description}
+
+## Quick Start
+
+```bash
+{installation command}
+```
+
+## Usage
+
+Always reference AGENTS.md in prompts:
+```
+"Follow @AGENTS.md standards. Implement [feature] with tests first (95%+ coverage)."
+```
+
+## Workflow
+
+1. Include AGENTS.md in context (tool-specific method)
+2. Request features with "@AGENTS.md" reference
+3. Review generated code
+4. Run quality checks: `npm run lint && npm test`
+
+**Critical**: Reference AGENTS.md for consistent standards.
+
+<!-- {TOOL}:END -->
+

package/templates/commands/rulebook-task-apply.md

@@ -0,0 +1,67 @@
+---
+name: /rulebook-task-apply
+id: rulebook-task-apply
+category: Rulebook
+description: Implement an approved Rulebook task and keep tasks checklist in sync.
+---
+<!-- RULEBOOK:START -->
+**Guardrails**
+- Favor straightforward, minimal implementations first and add complexity only when it is requested or clearly required.
+- Keep changes tightly scoped to the requested outcome.
+- Refer to `/rulebook/RULEBOOK.md` for complete task management guidelines.
+- **CRITICAL**: Update `tasks.md` IMMEDIATELY after completing and testing each implementation step.
+
+**Steps**
+Track these steps as TODOs and complete them one by one.
+
+1. **Read Task Details**:
+   ```bash
+   rulebook task show <task-id>
+   ```
+   Read `proposal.md`, `design.md` (if present), and `tasks.md` to confirm scope and acceptance criteria.
+
+2. **Follow Priority Order (MANDATORY)**:
+   - **Tests** (HIGHEST PRIORITY) - Write tests first
+   - **Coverage Verification** (CRITICAL) - Verify coverage ≥95%
+   - **Update Task Status** (MANDATORY) - Mark completed items as `[x]` in `tasks.md`
+   - **Next Task** (Only after above steps)
+
+3. **Work Through Tasks Sequentially**:
+   - Work through `tasks.md` checklist item by item
+   - Keep edits minimal and focused on the requested change
+   - Follow priority order (most critical first)
+
+4. **After Each Implementation Step**:
+   - ✅ Implement the feature
+   - ✅ Test the implementation
+   - ✅ Verify test coverage (run `npm test -- --coverage`)
+   - ✅ Update `tasks.md` IMMEDIATELY (mark as `[x]`)
+   - ✅ Commit locally (backup)
+   - ✅ Only then proceed to next task
+
+5. **Update Tasks Checklist**:
+   After completing and testing each item:
+   ```markdown
+   ## 1. Implementation Phase
+   - [x] 1.1 Create task manager module <!-- tested, coverage: 95% -->
+   - [x] 1.2 Add validation logic <!-- tested, coverage: 92%, status: complete -->
+   - [ ] 1.3 Add archive functionality <!-- next: will start after status update -->
+   ```
+
+6. **Confirm Completion**:
+   - Make sure every item in `tasks.md` is finished
+   - All tests pass
+   - Coverage meets thresholds
+   - Documentation updated
+
+7. **Update Checklist After All Work**:
+   - Mark each completed task as `[x]`
+   - Add comments with test status and coverage
+   - Reflect reality in the checklist
+
+**Reference**
+- Use `rulebook task show <task-id>` when additional context is required
+- Use `rulebook task validate <task-id>` to check format before archiving
+- See `/rulebook/RULEBOOK.md` for complete task management guidelines and priority order
+<!-- RULEBOOK:END -->
+

package/templates/commands/rulebook-task-archive.md

@@ -0,0 +1,70 @@
+---
+name: /rulebook-task-archive
+id: rulebook-task-archive
+category: Rulebook
+description: Archive a completed Rulebook task and apply spec deltas to main specifications.
+---
+<!-- RULEBOOK:START -->
+**Guardrails**
+- Favor straightforward, minimal implementations first and add complexity only when it is requested or clearly required.
+- Keep changes tightly scoped to the requested outcome.
+- Refer to `/rulebook/RULEBOOK.md` for complete task management guidelines.
+
+**Steps**
+1. **Verify Task Completion**:
+   - All items in `tasks.md` must be marked as `[x]`
+   - All tests must pass
+   - Code review complete (if applicable)
+   - Documentation updated (README, CHANGELOG, specs)
+
+2. **Run Quality Checks**:
+   ```bash
+   npm test
+   npm run lint
+   npm run type-check
+   npm run build
+   ```
+   Ensure all checks pass before archiving.
+
+3. **Validate Task Format**:
+   ```bash
+   rulebook task validate <task-id>
+   ```
+   Must pass all format checks.
+
+4. **Archive Task**:
+   ```bash
+   rulebook task archive <task-id>
+   ```
+   Or without prompts:
+   ```bash
+   rulebook task archive <task-id> --skip-validation
+   ```
+   (Only use `--skip-validation` if you're certain the task is valid)
+
+5. **Archive Process**:
+   - Validates task format (unless skipped)
+   - Checks task completion status
+   - Applies spec deltas to main specifications
+   - Moves task to `/rulebook/tasks/archive/YYYY-MM-DD-<task-id>/`
+   - Updates related specifications
+
+6. **Verify Archive**:
+   ```bash
+   rulebook task list --archived
+   ```
+   Task should appear in archived list.
+
+7. **Post-Archive Actions**:
+   - Ensure spec deltas are applied to main specifications
+   - Update CHANGELOG.md with the change
+   - Document any breaking changes
+   - Create migration guides (if needed)
+   - Unblock related tasks (if any)
+
+**Reference**
+- Use `rulebook task list --archived` to see archived tasks
+- Use `rulebook task show <task-id>` to view task details
+- See `/rulebook/RULEBOOK.md` for complete task management guidelines
+<!-- RULEBOOK:END -->
+

package/templates/commands/rulebook-task-create.md

@@ -0,0 +1,93 @@
+---
+name: /rulebook-task-create
+id: rulebook-task-create
+category: Rulebook
+description: Create a new Rulebook task following OpenSpec-compatible format with Context7 MCP validation.
+---
+<!-- RULEBOOK:START -->
+**Guardrails**
+- Favor straightforward, minimal implementations first and add complexity only when it is requested or clearly required.
+- Keep changes tightly scoped to the requested outcome.
+- Refer to `/rulebook/RULEBOOK.md` for complete task management guidelines and format requirements.
+- **CRITICAL**: Context7 MCP is REQUIRED for task creation to ensure correct OpenSpec-compatible format.
+- Identify any vague or ambiguous details and ask the necessary follow-up questions before editing files.
+
+**Steps**
+1. **Check Context7 MCP (MANDATORY)**: Query Context7 for OpenSpec documentation to get the official format:
+   ```
+   @Context7 /fission-ai/openspec task creation format spec structure
+   ```
+   Review official format requirements: spec delta format, requirement structure, scenario formatting, delta headers (ADDED/MODIFIED/REMOVED/RENAMED).
+
+2. **Explore Current State**: 
+   - Run `rulebook task list` to see existing tasks
+   - Review related code or docs (e.g., via `rg`/`ls`) to understand current behavior
+   - Note any gaps that require clarification
+
+3. **Choose Task ID**: Use verb-led kebab-case (e.g., `add-feature`, `update-api`, `refactor-module`). Must be unique.
+
+4. **Create Task Structure**:
+   ```bash
+   rulebook task create <task-id>
+   ```
+   This creates `/rulebook/tasks/<task-id>/` with:
+   - `proposal.md` - Why and what changes
+   - `tasks.md` - Implementation checklist
+   - `specs/` - Directory for spec deltas
+
+5. **Write Proposal** (`proposal.md`):
+   - **Why**: Minimum 20 characters explaining why this change is needed
+   - **What Changes**: Detailed description of what will change
+   - **Impact**: Affected specs, code, breaking changes, user benefits
+
+6. **Write Tasks Checklist** (`tasks.md`):
+   - Organize by phases (Implementation, Testing, Documentation)
+   - Use checkbox format: `- [ ] Task description`
+   - Include validation steps (tests, coverage checks)
+
+7. **Write Spec Delta** (`specs/<module>/spec.md`):
+   - Use `## ADDED|MODIFIED|REMOVED|RENAMED Requirements` headers
+   - Requirements MUST use `### Requirement: [Name]` with SHALL/MUST keywords
+   - Scenarios MUST use `#### Scenario:` (4 hashtags, NOT 3)
+   - Scenarios MUST use Given/When/Then structure
+   - Example:
+     ```markdown
+     ## ADDED Requirements
+     
+     ### Requirement: Feature Name
+     The system SHALL do something specific and testable.
+     
+     #### Scenario: Scenario Name
+     Given some precondition
+     When an action occurs
+     Then an expected outcome happens
+     ```
+
+8. **Validate Task**:
+   ```bash
+   rulebook task validate <task-id>
+   ```
+   Fix any validation errors before proceeding.
+
+9. **Verify Format**:
+   - Purpose section: ≥20 characters ✅
+   - Requirements: Contain SHALL or MUST ✅
+   - Scenarios: Use `#### Scenario:` (4 hashtags) ✅
+   - Scenarios: Use Given/When/Then structure ✅
+   - Delta headers: Use ADDED/MODIFIED/REMOVED/RENAMED ✅
+
+**Reference**
+- See `/rulebook/RULEBOOK.md` for complete task management guidelines
+- Use `rulebook task show <task-id>` to view task details
+- Use `rulebook task list` to see all tasks
+- Search existing requirements with `rg -n "Requirement:|Scenario:" rulebook/tasks` before writing new ones
+- Explore the codebase with `rg <keyword>`, `ls`, or direct file reads so proposals align with current implementation realities
+
+**Common Pitfalls to Avoid**
+- ❌ Using 3 hashtags for scenarios (`### Scenario:`) - MUST use 4 (`#### Scenario:`)
+- ❌ Missing SHALL/MUST keywords in requirements
+- ❌ Using bullet points for scenarios instead of Given/When/Then
+- ❌ Purpose section too short (<20 characters)
+- ❌ Wrong delta headers (use ADDED/MODIFIED/REMOVED/RENAMED, not "New Requirements" or "Changes")
+<!-- RULEBOOK:END -->
+