ace-docs 0.31.8 → 0.34.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 7fe19c8ea6a289f768e14c3e46975134e48c9e7a65d2b5ea8dd102257376c90c
-  data.tar.gz: fd85102c50de9546c5bd0fa8984a68c6303ac14124a091153aeb99c769b571d3
+  metadata.gz: ce697d65c80ba44319cf2484f1a5568981b81e5c205a8397bbf33b0dbd69b22d
+  data.tar.gz: 8b2846bcff7af3e21e5411fa2e3e3babd06b9dc5718075e2c046adac082d29dc
 SHA512:
-  metadata.gz: 0a3e7719cd422f90fbe83bda4c0e5fe4ef1ea7e94e3dc75fc204e69c0f76a7753238f63a890f61acc676789d19b1639dafdc6efa847f5e98ebfde8cacf82c3c6
-  data.tar.gz: 6f40652bd7b30532a4d536dbfa679f69357ceb61f709f55d7337a91c1b2db3e4aa2a2ad260b79ba3dc2eff945e6db4c006e1b7592dd26e224a3c46c0080a258b
+  metadata.gz: 3354a595ec9ab354ac641ab07ae5568dde41e938feda0a5f734b41015a001a069e6c5cdb6de4ee89c3a714189b4afbec99e72582bc8eb14f148df5d73645f7bd
+  data.tar.gz: 9c56bd30cc6bd9392461d3cb28669aac49b2d37e4c9e22de61f5d051b93de6da0aa823a8b3d6422dbe5a153aff79d148bfa4e07c4fa06b910ed3092ee88e8469

data/CHANGELOG.md

@@ -6,6 +6,44 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
 ## [Unreleased]
+## [0.34.1] - 2026-04-16
+
+### Fixed
+- Made `analyze-consistency` fail closed when no report file is produced and aligned E2E verification with explicit provider-unavailable evidence.
+
+## [0.34.0] - 2026-04-14
+
+### Added
+- Added a new goal-style `TS-DOCS-002-analysis-workflows` E2E scenario covering `ace-docs analyze` and `ace-docs analyze-consistency` command journeys with impact-first verification guidance.
+
+### Changed
+- Hardened `TS-DOCS-001` verifier expectations for discover/validate/status to prioritize seeded state and stable outcome semantics over brittle phrasing checks.
+- Expanded usage guidance for `analyze` and `analyze-consistency` with deterministic artifact/report location notes for reproducible CLI workflows.
+- Updated `analyze` and `analyze-consistency` command help text to document output/report artifact locations and accurate exit-code behavior.
+
+## [0.33.1] - 2026-04-13
+
+### Changed
+- Completed the batch i05 migration follow-through for this package and aligned it with the restarted `fast` / `feat` / `e2e` verification model.
+
+### Technical
+- Included in the coordinated assignment-driven patch release for batch i05 package updates.
+
+
+## [0.33.0] - 2026-04-12
+
+### Changed
+- Migrated `ace-docs` to the `fast` / `feat` / `e2e` testing model by moving deterministic coverage from legacy test paths into `test/fast` and `test/feat`, and aligning TS-DOCS-001 scenario metadata and runner/verifier assets with the new artifact contract.
+
+## [0.32.1] - 2026-04-10
+
+### Fixed
+- Restored docs-management ignore coverage for legacy `test/e2e/**/*.md` scenario markdown paths during the E2E path migration.
+
+## [0.32.0] - 2026-04-01
+
+### Changed
+- Removed active cookbook workflow ownership from `ace-docs` by deleting `create-cookbook.wf.md` and updating handbook catalog references.
 
 ## [0.31.8] - 2026-03-31
 

data/README.md

@@ -36,5 +36,28 @@
 
 **Enforce docs quality in release loops** - pair with [ace-lint](../ace-lint) for markdown checks and use `ace-docs` update workflows to keep guides, READMEs, and references in sync.
 
+For concrete analyze/update entry points and deterministic CLI examples, see the [Usage Guide](docs/usage.md#analyze) and the [analyze-and-update workflow examples](docs/usage.md#analyze-and-update-workflow).
+
+## Testing Contract
+
+Run deterministic package coverage with:
+
+```bash
+ace-test ace-docs
+ace-test ace-docs all
+```
+
+Run deterministic feature coverage:
+
+```bash
+ace-test ace-docs feat
+```
+
+Run retained workflow scenarios in E2E:
+
+```bash
+ace-test-e2e ace-docs
+```
+
 ---
 [Getting Started](docs/getting-started.md) | [Usage Guide](docs/usage.md) | [Handbook - Skills, Agents, Templates](docs/handbook.md) | Part of [ACE](https://github.com/cs3b/ace)

data/handbook/workflow-instructions/docs/update-roadmap.wf.md

@@ -11,13 +11,13 @@ ace-docs:
 
 ## Goal
 
-Synchronize the project roadmap (`.ace-taskflow/roadmap.md`) with the current state of releases and tasks in the `.ace-taskflow/` directory structure. This workflow analyzes release folders, updates the Planned Major Releases table, synchronizes cross-release dependencies, and maintains roadmap format compliance per the Roadmap Definition Guide.
+Synchronize the project roadmap (`.ace-task/roadmap.md`) with the current state of releases and tasks in the `.ace-task/` directory structure. This workflow analyzes release folders, updates the Planned Major Releases table, synchronizes cross-release dependencies, and maintains roadmap format compliance per the Roadmap Definition Guide.
 
 ## Prerequisites
 
-* `.ace-taskflow/roadmap.md` exists and follows roadmap-definition.g.md structure
-* `.ace-taskflow/` directory contains release folders with release.md files
-* `ace-taskflow` CLI tool available for release queries
+* `.ace-task/roadmap.md` exists and follows roadmap-definition.g.md structure
+* `.ace-task/` directory contains release folders with release.md files
+* `ace-task` CLI tool available for release queries
 * `ace-nav` available for workflow protocol support
 * Git repository in clean state for committing changes
 
@@ -33,7 +33,7 @@ Synchronize the project roadmap (`.ace-taskflow/roadmap.md`) with the current st
 
 ```bash
 # Get roadmap path
-cat .ace-taskflow/roadmap.md
+cat .ace-task/roadmap.md
 ```
 
 **Capture current state:**
@@ -73,14 +73,14 @@ cat .ace-taskflow/roadmap.md
 
 ### 3. Analyze Release State
 
-**Discover all releases in .ace-taskflow structure:**
+**Discover all releases in .ace-task structure:**
 
 ```bash
 # Get current release
 ace-release
 
 # List all release directories
-ls -d .ace-taskflow/v.*/ 2>/dev/null || echo "No releases found"
+ls -d .ace-task/v.*/ 2>/dev/null || echo "No releases found"
 ```
 
 **For each release found, extract:**
@@ -101,17 +101,17 @@ ls -d .ace-taskflow/v.*/ 2>/dev/null || echo "No releases found"
 **Synchronization Rules:**
 
 1. **Add New Releases:**
-   - If release exists in `.ace-taskflow/` but NOT in roadmap table
+   - If release exists in `.ace-task/` but NOT in roadmap table
    - Extract release information from release.md
    - Add row to Planned Major Releases table with proper format
 
 2. **Update Existing Releases:**
-   - If release exists in both roadmap and `.ace-taskflow/`
+   - If release exists in both roadmap and `.ace-task/`
    - Compare current information with release.md
    - Update any changed fields (goals, target window, epics)
 
 3. **Remove Completed Releases:**
-   - If release is marked done/completed in `.ace-taskflow/`
+   - If release is marked done/completed in `.ace-task/`
    - Remove entire row from Planned Major Releases table
    - Ensure release information captured in changelog
    - Document removal in Update History
@@ -140,7 +140,7 @@ ls -d .ace-taskflow/v.*/ 2>/dev/null || echo "No releases found"
    - Remove or update obsolete statements
 
 2. **Add new dependencies:**
-   - Analyze task dependencies from `.ace-taskflow/` structure
+   - Analyze task dependencies from `.ace-task/` structure
    - Identify cross-release blocking dependencies
    - Add clear dependency statements to Section 5
 
@@ -199,7 +199,7 @@ Add new row to Update History table (Section 6) at the TOP:
    - Version numbers use semantic versioning
 
 3. **Consistency Check:**
-   - Releases in table match `.ace-taskflow/` structure
+   - Releases in table match `.ace-task/` structure
    - Dependencies reference valid releases/epics
    - Update history reflects changes made
 
@@ -214,10 +214,10 @@ Add new row to Update History table (Section 6) at the TOP:
 
 ```bash
 # Review changes before committing
-git diff .ace-taskflow/roadmap.md
+git diff .ace-task/roadmap.md
 
 # Stage roadmap file
-git add .ace-taskflow/roadmap.md
+git add .ace-task/roadmap.md
 
 # Commit with descriptive message
 git commit -m "docs(roadmap): update planned releases and synchronize with current state"
@@ -229,7 +229,7 @@ git commit -m "docs(roadmap): update planned releases and synchronize with curre
 - Examples:
   - `docs(roadmap): add v.0.9.0 Mono-Repo to planned releases`
   - `docs(roadmap): remove completed v.0.8.0 from planned releases`
-  - `docs(roadmap): synchronize release status with .ace-taskflow structure`
+  - `docs(roadmap): synchronize release status with .ace-task structure`
 
 ## Error Handling
 
@@ -254,8 +254,8 @@ git commit -m "docs(roadmap): update planned releases and synchronize with curre
 - Inconsistent release naming
 
 **Recovery Steps:**
-1. Report discrepancies between `.ace-taskflow/` and roadmap
-2. Determine authoritative source (usually `.ace-taskflow/` structure)
+1. Report discrepancies between `.ace-task/` and roadmap
+2. Determine authoritative source (usually `.ace-task/` structure)
 3. Update roadmap to match actual release state
 4. Document assumptions in Update History
 
@@ -328,7 +328,7 @@ git commit -m "docs(roadmap): update planned releases and synchronize with curre
 ## Success Criteria
 
 - [ ] Roadmap format validated against roadmap-definition.g.md
-- [ ] Planned Major Releases table synchronized with `.ace-taskflow/` structure
+- [ ] Planned Major Releases table synchronized with `.ace-task/` structure
 - [ ] Completed releases removed from roadmap table
 - [ ] Cross-release dependencies updated and accurate
 - [ ] Front matter `last_reviewed` date updated to today
@@ -411,10 +411,10 @@ status: [draft|active|archived]
 ## References
 
 - **Roadmap Definition Guide**: `dev-handbook/guides/roadmap-definition.g.md`
-- **Current Roadmap**: `.ace-taskflow/roadmap.md`
+- **Current Roadmap**: `.ace-task/roadmap.md`
 - **Draft Release Workflow**: `wfi://release/draft`
 - **Publish Release Workflow**: `wfi://release/publish`
-- **ace-taskflow CLI**: For release queries and task analysis
+- **ace-task CLI**: For release queries and task analysis
 
 ---
 

data/handbook/workflow-instructions/docs/update-usage.wf.md

@@ -42,7 +42,7 @@ Systematically update usage documentation files based on user feedback, task req
      find . -name "usage.md" -path "*/ux/*" -o -name "usage.md" -path "*/docs/*"
 
      # Or check specific task folder
-     ls -la .ace-taskflow/v.*/t/*/ux/usage.md
+     ls -la .ace-task/v.*/t/*/ux/usage.md
      ```
    * Extract key requirements:
      - What needs to be documented
@@ -102,7 +102,7 @@ Systematically update usage documentation files based on user feedback, task req
    **Commands/Steps**:
    ```bash
    # Command with comments
-   ace-taskflow command --flag value
+   ace-task command --flag value
    ```
 
    **Expected Output**:
@@ -159,7 +159,7 @@ Systematically update usage documentation files based on user feedback, task req
    ### Bash CLI Commands
    Commands without `/` are terminal/bash commands:
    ```bash
-   ace-taskflow command
+   ace-task command
    ```
 
    ### Claude Code Commands (Slash Commands)
@@ -469,7 +469,7 @@ feature:
 **Available Commands:**
 - `/ace:[command1]` - [Description]
 - `/ace:[command2]` - [Description]
-- `ace-taskflow [command]` - [CLI equivalent if exists]
+- `ace-task [command]` - [CLI equivalent if exists]
 
 ## Command Types
 
@@ -482,7 +482,7 @@ Commands starting with `/` are executed **within Claude Code**:
 ### Bash CLI Commands
 Commands without `/` are **terminal/bash commands**:
 ```bash
-ace-taskflow [command]
+ace-task [command]
 ```
 
 ## Usage Scenarios
@@ -493,7 +493,7 @@ ace-taskflow [command]
 
 ```bash
 # Step 1: Preparation (bash command)
-ace-taskflow list
+ace-task list
 
 # Step 2: Execution (Claude command)
 /ace:[command]
@@ -538,13 +538,13 @@ Summary: 2 items completed
 [Sample output]
 ```
 
-### `ace-taskflow [command]`
+### `ace-task [command]`
 
 **Purpose**: [CLI tool purpose]
 
 **Usage**:
 ```bash
-ace-taskflow [command] [options]
+ace-task [command] [options]
 ```
 
 **Options**:
@@ -590,7 +590,7 @@ Friday: [Review]
 **Solution**:
 ```bash
 # Verify installation
-which ace-taskflow
+which ace-task
 
 # Check workflow exists
 ace-bundle wfi://[workflow] --verify

data/lib/ace/docs/cli/commands/analyze.rb

@@ -44,8 +44,9 @@ module Ace
               Project config: .ace/docs/config.yml
 
             Output:
-              Analysis results printed to stdout
-              Exit codes: 0 (success), 1 (error)
+              Prints an analysis summary and writes session artifacts to .ace-local/docs/analyze-<id>/
+              Key files: analysis.md, metadata.yml, prompt-system.md, prompt-user.md
+              Exit codes: 0 (success), 1 (error), 2 (no changes), 3 (analysis error)
           DESC
 
           example [

data/lib/ace/docs/cli/commands/analyze_consistency.rb

@@ -34,8 +34,9 @@ module Ace
               Project config: .ace/docs/config.yml
 
             Output:
-              Consistency report in markdown format (default)
-              Exit codes: 0 (success), 1 (issues found with --strict), 2 (error)
+              Prints report location and writes artifacts under .ace-local/docs/sessions/analyze-consistency-<timestamp>/
+              Key files: report.md, metadata.yml, documents.json
+              Exit codes: 0 (success), 1 (error)
           DESC
 
           example [

data/lib/ace/docs/organisms/cross_document_analyzer.rb

@@ -76,7 +76,9 @@ module Ace
           puts "This may take a few minutes for large document sets..." if documents.count > 10
           response = execute_llm_query(prompts, session_dir)
 
-          # Response is already saved to report.md by ace-llm's output option
+          unless response && File.exist?(response) && !File.read(response).strip.empty?
+            raise "Consistency analysis did not produce a completed report"
+          end
 
           # Save metadata for reference
           save_metadata(documents, pattern, session_dir)

data/lib/ace/docs/organisms/document_registry.rb

@@ -230,7 +230,7 @@ module Ace
             %r{^#{Regexp.escape(tmp_dir)}/},  # Only ignore <project_root>/tmp/
             %r{/coverage/},
             %r{/_legacy/},
-            %r{/\.ace-taskflow/done/}
+            %r{/\.ace-task/done/}
           ]
 
           # Add patterns from config if available

data/lib/ace/docs/version.rb

@@ -2,6 +2,6 @@
 
 module Ace
   module Docs
-    VERSION = '0.31.8'
+    VERSION = '0.34.1'
   end
 end

metadata

@@ -1,13 +1,13 @@
 --- !ruby/object:Gem::Specification
 name: ace-docs
 version: !ruby/object:Gem::Version
-  version: 0.31.8
+  version: 0.34.1
 platform: ruby
 authors:
 - Michal Czyz
 bindir: exe
 cert_chain: []
-date: 2026-04-01 00:00:00.000000000 Z
+date: 2026-04-20 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: ace-support-config
@@ -277,7 +277,6 @@ files:
 - handbook/templates/user-docs/user-guide.template.md
 - handbook/workflow-instructions/docs/create-adr.wf.md
 - handbook/workflow-instructions/docs/create-api.wf.md
-- handbook/workflow-instructions/docs/create-cookbook.wf.md
 - handbook/workflow-instructions/docs/create-user.wf.md
 - handbook/workflow-instructions/docs/maintain-adrs.wf.md
 - handbook/workflow-instructions/docs/squash-changelog.wf.md

data/handbook/workflow-instructions/docs/create-cookbook.wf.md

@@ -1,434 +0,0 @@
----
-doc-type: workflow
-title: Create Cookbook Workflow Instruction
-purpose: Documentation for ace-docs/handbook/workflow-instructions/docs/create-cookbook.wf.md
-ace-docs:
-  last-updated: 2026-02-23
-  last-checked: 2026-03-21
----
-
-# Create Cookbook Workflow Instruction
-
-**Goal:** Transform identified patterns and insights into reusable, high-quality cookbooks that accelerate future
-development work through systematic documentation of proven procedures.
-
-## Prerequisites
-
-* Understanding of cookbook purpose and target audience
-* Source material (reflection note, direct observation, or synthesis report)
-* Access to create files in project structure using `create-path` tool
-
-## Project Context Loading
-
-* Read and follow: `ace-bundle wfi://bundle`
-
-## High-Level Execution Plan
-
-### Planning Steps
-
-* Identify cookbook source material and
-  extract core patterns
-* Determine appropriate cookbook category
-  and target audience
-* Define cookbook scope and validation
-  criteria
-
-
-### Execution Steps
-
-* Create cookbook file using embedded
-  template and `create-path` tool
-* Populate cookbook sections with
-  structured content
-* Validate cookbook completeness and
-  actionability
-* Save cookbook in appropriate location
-  with standard naming
-
-
-## Process Steps
-
-1.  **Identify Source Material:**
-    * **From Reflection Note:** Extract reusable patterns and procedures
-    * **From Direct Input:** Document observed complex procedures
-    * **From Synthesis Report:** Capture common workflows and best practices
-    * **From User Input:** Accept pattern description and context details
-2.  **Select Cookbook Category:** Choose the primary category that best fits the pattern:
-    * **integration:** Connecting systems, services, or tools
-    * **setup:** Environment configuration and initialization
-    * **migration:** Moving between systems, versions, or structures
-    * **debugging:** Troubleshooting and problem resolution procedures
-    * **automation:** Streamlining repetitive tasks and workflows
-    * **pattern:** General development patterns and best practices
-3.  **Determine Target Audience:**
-    * **beginner:** Basic concepts, detailed explanations, minimal assumptions
-    * **intermediate:** Moderate complexity, some background knowledge assumed
-    * **advanced:** Complex procedures, expert-level understanding expected
-4.  **Define Cookbook Scope:**
-    * **Single Pattern:** Focus on one specific procedure or technique
-    * **Composite Pattern:** Multiple related procedures in logical sequence
-    * **Cross-Category Pattern:** Procedures spanning multiple areas (use primary + secondary categories)
-5.  **Generate Cookbook File:** # Create cookbook file (adjust path to your project's documentation structure)
-    create-path file "docs/cookbooks/\[category\]-\[descriptive-name\].cookbook.md"   
-     --title "\[Category\] Cookbook: \[Descriptive Name\]" # Or create manually using the embedded template below
-    {: .language-bash}
-
-6.  **Populate Cookbook Content:** Using the embedded template structure, fill in:
-    * **Purpose**: Clear statement of what the cookbook accomplishes
-    * **Prerequisites**: System, knowledge, and tool requirements
-    * **Steps**: Detailed, actionable procedures with validation
-    * **Examples**: Concrete use cases and implementations
-    * **Troubleshooting**: Common issues and their solutions
-    * **Validation**: Success criteria and testing procedures
-7.  **Review and Validate:**
-    * Ensure all sections have meaningful content
-    * Verify steps are actionable and complete
-    * Test examples and validation procedures
-    * Confirm naming follows convention: `[category]-[descriptive-name].cookbook.md`
-
-## Cookbook Categories & Naming Examples
-
-### Category: integration
-
-* `integration-oauth-provider.cookbook.md` - OAuth provider setup and configuration
-* `integration-api-gateway.cookbook.md` - API gateway implementation patterns
-* `integration-webhook-handling.cookbook.md` - Webhook endpoint design and testing
-
-### Category: setup
-
-* `setup-development-environment.cookbook.md` - Complete dev environment configuration
-* `setup-ci-cd-pipeline.cookbook.md` - Continuous integration/deployment setup
-* `setup-monitoring-stack.cookbook.md` - Observability and monitoring configuration
-
-### Category: migration
-
-* `migration-database-schema.cookbook.md` - Database schema migration procedures
-* `migration-legacy-api.cookbook.md` - Legacy API modernization approach
-* `migration-cloud-infrastructure.cookbook.md` - Infrastructure migration patterns
-
-### Category: debugging
-
-* `debugging-performance-issues.cookbook.md` - Performance bottleneck investigation
-* `debugging-memory-leaks.cookbook.md` - Memory leak detection and resolution
-* `debugging-distributed-systems.cookbook.md` - Multi-service debugging techniques
-
-### Category: automation
-
-* `automation-test-data-generation.cookbook.md` - Automated test data creation
-* `automation-deployment-rollback.cookbook.md` - Automated rollback procedures
-* `automation-code-quality-gates.cookbook.md` - Automated quality assurance
-
-### Category: pattern
-
-* `pattern-error-handling.cookbook.md` - Consistent error handling approaches
-* `pattern-caching-strategy.cookbook.md` - Caching implementation patterns
-* `pattern-service-communication.cookbook.md` - Inter-service communication patterns
-
-## Error Handling
-
-### Missing Source Material
-
-**Symptoms:** No clear pattern or procedure identified **Recovery:**
-
-1.  Prompt user for pattern details and context
-2.  Ask clarifying questions about the procedure
-3.  Guide through pattern identification process
-
-### Duplicate Cookbook Name
-
-**Symptoms:** File already exists with same name **Recovery:**
-
-1.  Check existing cookbook content for overlap
-2.  Suggest alternative naming with version or specialization
-3.  Consider merging patterns if highly related
-4.  Use `--force` flag only if intentional replacement
-
-### Invalid Category
-
-**Symptoms:** Category doesn't match standard list **Recovery:**
-
-1.  Show available categories with descriptions
-2.  Help user select most appropriate primary category
-3.  Note secondary category in cookbook metadata if cross-category
-
-### Incomplete Pattern Documentation
-
-**Symptoms:** Pattern lacks sufficient detail for actionable cookbook **Recovery:**
-
-1.  Request additional context and examples
-2.  Break down complex pattern into smaller, manageable steps
-3.  Identify missing prerequisites or validation steps
-
-<documents>
-    <template name="cookbook"># [Category] Cookbook: [Descriptive Name]
-
-**Created**: YYYY-MM-DD
-**Last Updated**: YYYY-MM-DD
-**Category**: [integration | setup | migration | debugging | automation | pattern]
-**Audience**: [beginner | intermediate | advanced]
-**Estimated Time**: [X hours/minutes]
-
-## Purpose
-
-Brief description of what this cookbook accomplishes and why it's valuable.
-
-## Prerequisites
-
-**System Requirements:**
-- Requirement 1
-- Requirement 2
-
-**Knowledge Requirements:**
-- Knowledge area 1
-- Knowledge area 2
-
-**Tools & Dependencies:**
-- Tool/dependency 1
-- Tool/dependency 2
-
-## Overview
-
-High-level summary of the approach and main steps involved.
-
-## Steps
-
-### Step 1: [Step Title]
-
-**Objective**: What this step accomplishes
-
-**Commands/Actions:**
-```bash
-# Command examples with explanation
-command --option value
-```
-
-**Expected Output:**
-```
-Sample output that confirms success
-```
-
-**Validation:**
-```bash
-# Commands to verify this step completed successfully
-verification-command
-```
-
-**Troubleshooting:**
-- Common issue 1: Solution
-- Common issue 2: Solution
-
-### Step 2: [Step Title]
-
-**Objective**: What this step accomplishes
-
-**Commands/Actions:**
-```bash
-# Additional commands
-```
-
-**Expected Output:**
-```
-Expected results
-```
-
-**Validation:**
-```bash
-# Verification commands
-```
-
-**Troubleshooting:**
-- Issue: Solution
-
-## Validation & Testing
-
-### Final Validation Steps
-
-1. **System Check:**
-   ```bash
-   # Commands to verify overall system state
-   ```
-
-2. **Functional Test:**
-   ```bash
-   # Commands to test functionality end-to-end
-   ```
-
-3. **Performance Check** (if applicable):
-   ```bash
-   # Commands to verify performance expectations
-   ```
-
-### Success Criteria
-
-- [ ] Criterion 1: Description of what should be working
-- [ ] Criterion 2: Another measurable outcome
-- [ ] Criterion 3: Final validation point
-
-## Examples
-
-### Example 1: [Scenario Name]
-
-**Context**: Specific use case or scenario
-
-**Implementation:**
-```bash
-# Specific commands for this example
-```
-
-**Result**: What the outcome looks like
-
-### Example 2: [Another Scenario]
-
-**Context**: Different use case
-
-**Implementation:**
-```bash
-# Alternative approach or configuration
-```
-
-**Result**: Expected outcome
-
-## Templates & Code Snippets
-
-### Configuration Template
-
-```yaml
-# Sample configuration file
-key: value
-section:
-  nested_key: nested_value
-```
-
-### Code Template
-
-```ruby
-# Sample code implementation
-class ExampleClass
-  def example_method
-    # Implementation
-  end
-end
-```
-
-## Common Patterns
-
-### Pattern 1: [Pattern Name]
-
-**When to use**: Specific conditions or scenarios
-**How to implement**: Brief implementation guide
-**Example**: Quick code or command example
-
-### Pattern 2: [Another Pattern]
-
-**When to use**: Different scenario
-**How to implement**: Implementation approach
-**Example**: Sample usage
-
-## Troubleshooting
-
-### Error: [Common Error Message]
-
-**Symptoms**: How this error manifests
-**Cause**: Root cause of the issue
-**Solution**: Step-by-step fix
-**Prevention**: How to avoid in the future
-
-### Issue: [Common Problem]
-
-**Symptoms**: Observable behavior
-**Diagnosis**: How to confirm this is the issue
-**Resolution**: Solution steps
-**Verification**: How to confirm it's fixed
-
-## Related Resources
-
-### Documentation Links
-
-- [Official docs link](url)
-- [API reference](url)
-- [Community guide](url)
-
-### Other Cookbooks
-
-- [Related cookbook 1](link)
-- [Related cookbook 2](link)
-
-### External Tools & Resources
-
-- [Tool name](url): Description of how it helps
-- [Resource name](url): What it provides
-
-## Version History
-
-### v1.0 (YYYY-MM-DD)
-- Initial version
-- Core steps documented
-
-### v1.1 (YYYY-MM-DD)
-- Added troubleshooting section
-- Updated validation steps
-
-## Feedback & Improvements
-
-**Known Limitations:**
-- Limitation 1: Description and potential workaround
-- Limitation 2: Impact and mitigation
-
-**Future Enhancements:**
-- Enhancement idea 1
-- Enhancement idea 2
-
-**Contributing:**
-If you find issues or improvements for this cookbook, please:
-1. Document the specific issue or enhancement
-2. Test any proposed changes
-3. Update relevant sections
-4. Increment version number
-
----
-
-*This cookbook is part of the development workflow documentation.*
-    </template>
-</documents>
-
-## Input
-
-* Source material (reflection note path, synthesis report, or direct pattern description)
-* Cookbook category selection
-* Target audience level
-* Pattern scope and context
-
-## Output / Success Criteria
-
-* Cookbook file created in project documentation directory (e.g., `docs/cookbooks/`)
-* File follows naming convention: `[category]-[descriptive-name].cookbook.md`
-* All template sections populated with meaningful content
-* Cookbook is actionable and self-contained
-* Validation procedures included and tested
-* Related resources and cross-references updated
-
-## Common Patterns
-
-### Template-Driven Creation
-
-1.  Use `create-path` tool with cookbook template
-2.  Fill template sections systematically
-3.  Validate completeness against checklist
-4.  Test examples and procedures
-
-### Pattern Extraction
-
-1.  Analyze source material for recurring procedures
-2.  Identify decision points and alternatives
-3.  Document assumptions and prerequisites
-4.  Create concrete examples and test cases
-
-## Related Workflows
-
-* Integration with `create-path` tool for file generation (if available in your project)
-
-* * *
-
-This workflow systematically transforms development insights into reusable cookbooks, building a knowledge base that
-improves team efficiency and consistency across projects.
-