[pull] main from PaulDuvall:main

README.md

@@ -630,8 +630,10 @@ Attempting to solve complex data analysis, system integration, or real-time prob
 
 ## Issue Generation
 
-**Maturity**: Intermediate  
-**Description**: Generate Kanban-optimized work items (4-8 hours max) from requirements using AI to ensure continuous flow with clear acceptance criteria and dependencies.
+**Maturity**: Intermediate
+**Description**: Generate small, deployable work items (<1 hour with AI assistance) from requirements using AI to ensure continuous delivery with clear acceptance criteria and dependency tracking.
+
+**Methodology Note**: This pattern aligns well with Kanban principles (continuous flow, small batches) but works with any development methodology including Scrum, Scrumban, or ad-hoc workflows.
 
 **Related Patterns**: [Readiness Assessment](#readiness-assessment), [Spec-Driven Development](#spec-driven-development)
 
@@ -641,19 +643,19 @@ Attempting to solve complex data analysis, system integration, or real-time prob
 graph TD
     A[Requirements Document] --> B[AI Feature Analysis]
     B --> C[Work Item Splitting]
-    C --> D{<8 hours?}
+    C --> D{<1 hour?}
     D -->|No| E[Split Further]
     E --> C
     D -->|Yes| F[Story Generation]
     F --> G[Acceptance Criteria]
     G --> H[Cycle Time Target]
     H --> I[Dependency Mapping]
-    I --> J[Kanban Card Creation]
+    I --> J[Work Item Creation]
 ```
 
 **Core Principles**
 
-- **Kanban Optimization**: Each work item sized for <8 hours to ensure continuous flow
+- **Small Batch Sizing**: Each work item sized for <1 hour (AI-assisted development velocity) to enable continuous delivery and rapid feedback
 - **AI-Assisted Decomposition**: Use AI to break down requirements into implementable tasks
 - **Traceability Integration**: Connect issues to implementation files and CI workflows
 - **Dependency Mapping**: Establish clear relationships between work items and epics
@@ -663,7 +665,7 @@ graph TD
 
 Generated issues must include:
 - **Title**: Specific, actionable description of the work
-- **Cycle Time Target**: Estimated completion time (4-8 hours)
+- **Cycle Time Target**: Estimated completion time (<1 hour with AI assistance)
 - **Acceptance Criteria**: Testable conditions for completion
 - **File Scope**: Which files will be added, updated, or removed
 - **CI Requirements**: Test coverage, pipeline steps, quality gates
@@ -678,11 +680,10 @@ Generated issues must include:
 
 **Implementation Examples**: See [examples/issue-generation/](examples/issue-generation/) for detailed AI prompts, epic breakdown workflows, CI integration patterns, and traceability implementations. For AI-first workflows, see [Beads guide](examples/issue-generation/beads-guide.md) - a git-native issue tracker with CLI access and persistent agent memory.
 
-> "If a task takes more than one day, split it."
-> – Kanban Guide, Lean Kanban University
-
 > "Small, frequent deliveries expose issues early and keep teams aligned."
-> – Agile Alliance, Kanban Glossary
+> – Agile Alliance
+
+**Kanban Context**: This pattern embodies Kanban principles of continuous flow and small batch sizes. If using Kanban: "If a task takes more than one day, split it." (Kanban Guide, Lean Kanban University). However, the pattern works equally well with Scrum sprints, continuous delivery, or any methodology that values incremental progress.
 
 **Anti-pattern: Under-Specified Issues**
 Creating generic tasks without specific acceptance criteria, proper sizing, or clear dependencies leads to scope creep and estimation errors.
@@ -697,13 +698,14 @@ Creating issues without CI workflow integration, file tracking, or traceability
 ❌ "Add some tests"
 ❌ "AUTH-002: Implement password validation" (no file tracking or CI requirements)
 
-✅ "Add OAuth 2.0 token validation endpoint (8 hours)"
-✅ "Implement dashboard metric WebSocket connection (6 hours)"
-✅ "Write unit tests for user service login method (4 hours)"
+✅ "Add OAuth 2.0 token validation endpoint (<1 hour with AI)"
+✅ "Implement dashboard metric WebSocket connection (45 minutes)"
+✅ "Write unit tests for user service login method (30 minutes)"
 ✅ "AUTH-002: Password validation service with CI integration"
    - Files: src/auth/validators.py, tests/test_validators.py
    - Coverage: 95%, unit + integration tests
    - CI: lint, test, security-scan must pass
+   - AI-assisted: Use AI for implementation and test generation
 ```
 
 ---