claude-code-workflow 7.2.30 → 7.3.0

package/.claude/skills/ccw-chain/phases/spec-generator/phases/05-epics-stories.md

@@ -1,178 +0,0 @@
-# Phase 5: Epics & Stories
-
-Decompose the specification into executable Epics and Stories with dependency mapping.
-
-## Objective
-
-- Group requirements into 3-7 logical Epics
-- Tag MVP subset of Epics
-- Generate 2-5 Stories per Epic in standard user story format
-- Map cross-Epic dependencies (Mermaid diagram)
-- Generate epics.md using template
-
-## Input
-
-- Dependency: `{workDir}/requirements/_index.md`, `{workDir}/architecture/_index.md` (and individual files)
-- Reference: `{workDir}/product-brief.md`
-- Config: `{workDir}/spec-config.json`
-- Template: `templates/epics-template.md` (directory structure: `_index.md` + `EPIC-*.md`)
-
-## Execution Steps
-
-### Step 0: Load Validation Context
-
-Run `ccw spec load --category validation` for verification rules and acceptance criteria to validate epic decomposition.
-
-### Step 1: Load Phase 2-4 Context
-
-```javascript
-const specConfig = JSON.parse(Read(`${workDir}/spec-config.json`));
-const productBrief = Read(`${workDir}/product-brief.md`);
-const requirements = Read(`${workDir}/requirements.md`);
-const architecture = Read(`${workDir}/architecture.md`);
-
-let glossary = null;
-try {
-  glossary = JSON.parse(Read(`${workDir}/glossary.json`));
-} catch (e) { /* proceed without */ }
-```
-
-### Step 2: Epic Decomposition via Gemini CLI
-
-```javascript
-Bash({
-  command: `ccw cli -p "PURPOSE: Decompose requirements into executable Epics and Stories for implementation planning.
-Success: 3-7 Epics with prioritized Stories, dependency map, and MVP subset clearly defined.
-
-PRODUCT BRIEF (summary):
-${productBrief.slice(0, 2000)}
-
-REQUIREMENTS:
-${requirements.slice(0, 5000)}
-
-ARCHITECTURE (summary):
-${architecture.slice(0, 3000)}
-
-TASK:
-- Group requirements into 3-7 logical Epics:
-  - Each Epic: EPIC-NNN ID, title, description, priority (Must/Should/Could)
-  - Group by functional domain or user journey stage
-  - Tag MVP Epics (minimum set for initial release)
-  
-- For each Epic, generate 2-5 Stories:
-  - Each Story: STORY-{EPIC}-NNN ID, title
-  - User story format: As a [persona], I want [action] so that [benefit]
-  - 2-4 acceptance criteria per story (testable)
-  - Relative size estimate: S/M/L/XL
-  - Trace to source requirement(s): REQ-NNN
-  
-- Create dependency map:
-  - Cross-Epic dependencies (which Epics block others)
-  - Mermaid graph LR format
-  - Recommended execution order with rationale
-  
-- Define MVP:
-  - Which Epics are in MVP
-  - MVP definition of done (3-5 criteria)
-  - What is explicitly deferred post-MVP
-
-MODE: analysis
-EXPECTED: Structured output with: Epic list (ID, title, priority, MVP flag), Stories per Epic (ID, user story, AC, size, trace), dependency Mermaid diagram, execution order, MVP definition
-CONSTRAINTS:
-- Every Must-have requirement must appear in at least one Story
-- Stories must be small enough to implement independently (no XL stories in MVP)
-- Dependencies should be minimized across Epics
-\${glossary ? \`- Maintain terminology consistency with glossary: \${glossary.terms.map(t => t.term).join(', ')}\` : ''}
-" --tool gemini --mode analysis`,
-  run_in_background: true
-});
-
-// Wait for CLI result
-```
-
-### Step 3: Interactive Validation (Optional)
-
-```javascript
-if (!autoMode) {
-  // Present Epic overview table and dependency diagram
-  AskUserQuestion({
-    questions: [
-      {
-        question: "Review the Epic breakdown. Any adjustments needed?",
-        header: "Epics",
-        multiSelect: false,
-        options: [
-          { label: "Looks good", description: "Epic structure is appropriate" },
-          { label: "Merge epics", description: "Some epics should be combined" },
-          { label: "Split epic", description: "An epic is too large, needs splitting" },
-          { label: "Adjust MVP", description: "Change which epics are in MVP" }
-        ]
-      }
-    ]
-  });
-  // Apply user adjustments
-}
-```
-
-### Step 4: Generate epics/ directory
-
-```javascript
-const template = Read('templates/epics-template.md');
-
-// Create epics directory
-Bash(`mkdir -p "${workDir}/epics"`);
-
-const status = autoMode ? 'complete' : 'draft';
-const timestamp = new Date().toISOString();
-
-// Parse CLI output into structured Epics
-const epicsList = parseEpics(cliOutput);  // [{id, slug, title, priority, mvp, size, stories[], reqs[], adrs[], deps[]}]
-
-// Step 4a: Write individual EPIC-*.md files (one per Epic, stories included)
-epicsList.forEach(epic => {
-  // Use EPIC-NNN-{slug}.md template from templates/epics-template.md
-  // Fill: id, title, priority, mvp, size, description, requirements links,
-  //       architecture links, dependency links, stories with user stories + AC
-  Write(`${workDir}/epics/EPIC-${epic.id}-${epic.slug}.md`, epicContent);
-});
-
-// Step 4b: Write _index.md (overview + dependency map + MVP scope + traceability)
-// Use _index.md template from templates/epics-template.md
-// Fill: epic overview table (with links), dependency Mermaid diagram,
-//       execution order, MVP scope, traceability matrix, estimation summary
-Write(`${workDir}/epics/_index.md`, indexContent);
-
-// Update spec-config.json
-specConfig.phasesCompleted.push({
-  phase: 5,
-  name: "epics-stories",
-  output_dir: "epics/",
-  output_index: "epics/_index.md",
-  file_count: epicsList.length + 1,
-  completed_at: timestamp
-});
-Write(`${workDir}/spec-config.json`, JSON.stringify(specConfig, null, 2));
-```
-
-## Output
-
-- **Directory**: `epics/`
-  - `_index.md` — Overview table, dependency map, MVP scope, traceability matrix, links
-  - `EPIC-NNN-{slug}.md` — Individual Epic with Stories (per Epic)
-- **Format**: Markdown with YAML frontmatter, cross-linked to requirements and architecture via relative paths
-
-## Quality Checklist
-
-- [ ] 3-7 Epic files with EPIC-NNN IDs
-- [ ] >= 1 Epic tagged as MVP in frontmatter
-- [ ] 2-5 Stories per Epic file
-- [ ] Stories use "As a...I want...So that..." format
-- [ ] `_index.md` has cross-Epic dependency map (Mermaid)
-- [ ] `_index.md` links to all individual Epic files
-- [ ] Relative sizing (S/M/L/XL) per Story
-- [ ] Epic files link to requirement files and ADR files
-- [ ] All files have valid YAML frontmatter
-
-## Next Phase
-
-Proceed to [Phase 6: Readiness Check](06-readiness-check.md) to validate the complete specification package.

package/.claude/skills/ccw-chain/phases/spec-generator/phases/06-5-auto-fix.md

@@ -1,144 +0,0 @@
-# Phase 6.5: Auto-Fix
-
-Automatically repair specification issues identified in Phase 6 Readiness Check.
-
-## Objective
-
-- Parse readiness-report.md to extract Error and Warning items
-- Group issues by originating Phase (2-5)
-- Re-generate affected sections with error context injected into CLI prompts
-- Re-run Phase 6 validation after fixes
-
-## Input
-
-- Dependency: `{workDir}/readiness-report.md` (Phase 6 output)
-- Config: `{workDir}/spec-config.json` (with iteration_count)
-- All Phase 2-5 outputs
-
-## Execution Steps
-
-### Step 1: Parse Readiness Report
-
-```javascript
-const readinessReport = Read(`${workDir}/readiness-report.md`);
-const specConfig = JSON.parse(Read(`${workDir}/spec-config.json`));
-
-// Load glossary for terminology consistency during fixes
-let glossary = null;
-try {
-  glossary = JSON.parse(Read(`${workDir}/glossary.json`));
-} catch (e) { /* proceed without */ }
-
-// Extract issues from readiness report
-// Parse Error and Warning severity items
-// Group by originating phase:
-//   Phase 2 issues: vision, problem statement, scope, personas
-//   Phase 3 issues: requirements, acceptance criteria, priority, traceability
-//   Phase 4 issues: architecture, ADRs, tech stack, data model, state machine
-//   Phase 5 issues: epics, stories, dependencies, MVP scope
-
-const issuesByPhase = {
-  2: [], // product brief issues
-  3: [], // requirements issues
-  4: [], // architecture issues
-  5: []  // epics issues
-};
-
-// Parse structured issues from report
-// Each issue: { severity: "Error"|"Warning", description: "...", location: "file:section" }
-
-// Map phase numbers to output files
-const phaseOutputFile = {
-  2: 'product-brief.md',
-  3: 'requirements/_index.md',
-  4: 'architecture/_index.md',
-  5: 'epics/_index.md'
-};
-```
-
-### Step 2: Fix Affected Phases (Sequential)
-
-For each phase with issues (in order 2 -> 3 -> 4 -> 5):
-
-```javascript
-for (const [phase, issues] of Object.entries(issuesByPhase)) {
-  if (issues.length === 0) continue;
-
-  const errorContext = issues.map(i => `[${i.severity}] ${i.description} (at ${i.location})`).join('\n');
-
-  // Read current phase output
-  const currentOutput = Read(`${workDir}/${phaseOutputFile[phase]}`);
-
-  Bash({
-    command: `ccw cli -p "PURPOSE: Fix specification issues identified in readiness check for Phase ${phase}.
-Success: All listed issues resolved while maintaining consistency with other documents.
-
-CURRENT DOCUMENT:
-${currentOutput.slice(0, 5000)}
-
-ISSUES TO FIX:
-${errorContext}
-
-${glossary ? `GLOSSARY (maintain consistency):
-${JSON.stringify(glossary.terms, null, 2)}` : ''}
-
-TASK:
-- Address each listed issue specifically
-- Maintain all existing content that is not flagged
-- Ensure terminology consistency with glossary
-- Preserve YAML frontmatter and cross-references
-- Use RFC 2119 keywords for behavioral requirements
-- Increment document version number
-
-MODE: analysis
-EXPECTED: Corrected document content addressing all listed issues
-CONSTRAINTS: Minimal changes - only fix flagged issues, do not restructure unflagged sections
-" --tool gemini --mode analysis`,
-    run_in_background: true
-  });
-
-  // Wait for result, apply fixes to document
-  // Update document version in frontmatter
-}
-```
-
-### Step 3: Update State
-
-```javascript
-specConfig.phasesCompleted.push({
-  phase: 6.5,
-  name: "auto-fix",
-  iteration: specConfig.iteration_count,
-  phases_fixed: Object.keys(issuesByPhase).filter(p => issuesByPhase[p].length > 0),
-  completed_at: new Date().toISOString()
-});
-Write(`${workDir}/spec-config.json`, JSON.stringify(specConfig, null, 2));
-```
-
-### Step 4: Re-run Phase 6 Validation
-
-```javascript
-// Re-execute Phase 6: Readiness Check
-// This creates a new readiness-report.md
-// If still Fail and iteration_count < 2: loop back to Step 1
-// If Pass or iteration_count >= 2: proceed to handoff
-```
-
-## Output
-
-- **Updated**: Phase 2-5 documents (only affected ones)
-- **Updated**: `spec-config.json` (iteration tracking)
-- **Triggers**: Phase 6 re-validation
-
-## Quality Checklist
-
-- [ ] All Error-severity issues addressed
-- [ ] Warning-severity issues attempted (best effort)
-- [ ] Document versions incremented for modified files
-- [ ] Terminology consistency maintained
-- [ ] Cross-references still valid after fixes
-- [ ] Iteration count not exceeded (max 2)
-
-## Next Phase
-
-Re-run [Phase 6: Readiness Check](06-readiness-check.md) to validate fixes.