5-phase-workflow 1.1.1 → 1.2.0

package/src/templates/workflow/FEATURE-SPEC.md

@@ -0,0 +1,83 @@
+# Feature: {TICKET-ID} - {Title}
+
+## Ticket ID
+{TICKET-ID}
+
+## Summary
+{1-2 sentence overview of what will be implemented}
+
+## Problem Statement
+{Why is this feature needed? What problem does it solve?}
+
+## Requirements
+
+### Functional Requirements
+- {Requirement 1}
+- {Requirement 2}
+- ...
+
+### Non-Functional Requirements
+- {Performance requirements}
+- {Compatibility requirements}
+- ...
+
+## Constraints
+- {Business constraints}
+- {Technical constraints}
+- {Time/resource constraints}
+
+## Affected Components
+- **{component/module-1}** - {What changes here}
+- **{component/module-2}** - {What changes here}
+- **{component/module-3}** - {What changes here}
+- ...
+
+## Entity/Component Definitions
+
+### {EntityName} (if applicable)
+| Field | Type | Required | Description |
+|-------|------|----------|-------------|
+| id | {Entity}Id | Yes | Unique identifier |
+| name | String | Yes | Entity name |
+| ... | ... | ... | ... |
+
+### Business Rules
+- {Rule 1}
+- {Rule 2}
+- ...
+
+## Acceptance Criteria
+- [ ] {Criterion 1 - how to verify success}
+- [ ] {Criterion 2}
+- [ ] {Criterion 3}
+- ...
+
+## Alternatives Considered
+
+### Option 1: {Alternative approach}
+**Pros:** {Benefits}
+**Cons:** {Drawbacks}
+**Decision:** Rejected because {reason}
+
+### Option 2: {Another alternative}
+**Pros:** {Benefits}
+**Cons:** {Drawbacks}
+**Decision:** Rejected because {reason}
+
+### Chosen Approach: {Selected approach}
+**Rationale:** {Why this approach was chosen}
+
+## Questions & Answers
+
+### Q1: {Question from collaboration phase}
+**A:** {Answer from developer}
+
+### Q2: {Question}
+**A:** {Answer}
+
+...
+
+## Next Steps
+After approval:
+1. Run `/clear` to reset context
+2. Run `/5:plan-implementation {TICKET-ID}-{description}`

package/src/templates/workflow/FIX-PLAN.md

@@ -0,0 +1,55 @@
+# Fix Plan: {TICKET-ID}
+
+**Feature:** {feature-name}
+**Generated:** {timestamp}
+**Verification Status:** PARTIAL | FAILED
+
+---
+
+## Infrastructure Fixes
+
+{If no infrastructure issues: "No infrastructure issues found."}
+
+| # | File | Issue | Fix | Complexity |
+|---|------|-------|-----|------------|
+| 1 | {path} | {description} | {what to do} | simple / moderate / complex |
+
+## Feature Gap Fixes
+
+{If no feature gaps or Layer 2 was skipped: "No feature gaps found." or "Skipped — no feature.md available."}
+
+| # | File | Issue | Fix | Complexity |
+|---|------|-------|-----|------------|
+| 1 | {path} | {criterion or requirement not met} | {what to change} | simple / moderate / complex |
+
+## Quality Fixes
+
+{If no quality issues: "No quality issues found."}
+
+| # | File | Issue | Fix | Complexity |
+|---|------|-------|-----|------------|
+| 1 | {test-file-path} | No test file for {component} | Create test file | simple / moderate |
+
+---
+
+## Summary
+
+| Category | Count |
+|----------|-------|
+| Infrastructure | {N} |
+| Feature Gaps | {N} |
+| Quality | {N} |
+| **Total** | **{N}** |
+
+---
+
+## Results
+
+{Populated after fixes are applied}
+
+| # | File | Fix | Status |
+|---|------|----|--------|
+| 1 | {path} | {description} | APPLIED / FAILED |
+
+**Build after fixes:** {status}
+**Tests after fixes:** {status}

package/src/templates/workflow/PLAN.md

@@ -0,0 +1,30 @@
+---
+ticket: {TICKET-ID}
+feature: {feature-name}
+created: {ISO-timestamp}
+---
+
+# Implementation Plan: {TICKET-ID}
+
+{One sentence summary of what this plan builds}
+
+## Components
+
+| Step | Component | Action | File | Description | Complexity |
+|------|-----------|--------|------|-------------|------------|
+| 1 | {name} | create | {path} | {what it does} | simple |
+| 1 | {name} | create | {path} | {what it does} | simple |
+| 2 | {name} | create | {path} | {what it does} | moderate |
+| 2 | {name} | modify | {path} | {what to change} | moderate |
+| 3 | {name} | create | {path} | {what it does} | complex |
+
+## Implementation Notes
+
+- Follow the pattern from {existing-file} for {component-type}
+- {Key business rule to remember}
+- {Integration point to wire up}
+
+## Verification
+
+- Build: {command or "auto"}
+- Test: {command or "auto"}

package/src/templates/workflow/QUICK-PLAN.md

@@ -0,0 +1,17 @@
+# Quick Implementation: {TICKET-ID}
+
+## Task
+{DESCRIPTION}
+
+## Components
+
+| # | Type | Name | Skill | Module |
+|---|------|------|-------|--------|
+| 1 | {type} | {name} | {skill} | {module} |
+
+## Affected Modules
+- {module-1}
+- {module-2}
+
+## Execution
+{parallel | sequential | direct}

package/src/templates/workflow/REVIEW-FINDINGS.md

@@ -0,0 +1,58 @@
+# Code Review Findings
+
+**Generated:** {ISO-timestamp}
+**Scope:** {what was reviewed}
+**Total Findings:** {N}
+
+---
+
+## How to Use This File
+
+1. Review each finding below
+2. For each finding, choose an action:
+   - `[FIX]` - Apply this fix automatically (leave as-is)
+   - `[SKIP]` - Don't apply this fix (change FIX to SKIP)
+   - `[MANUAL]` - Custom instructions (change FIX to MANUAL and add instructions)
+3. Save this file
+4. Run: `/review-code apply`
+
+The apply command will read your annotations and apply marked fixes.
+
+---
+
+## Finding {N}/{total}
+
+**File:** {file-path}
+**Line:** {line-number}
+**Category:** {Fixable|Question|Manual}
+**Severity:** {error|warning|suggestion}
+
+**Description:**
+{what the reviewer found}
+
+**Suggested Fix:**
+{how to fix it - can be multi-line}
+
+**Original Reviewer Message:**
+```
+{raw output from reviewer}
+```
+
+**Action:** [FIX]
+
+**Custom Instructions:** (only if you selected [MANUAL])
+<!-- Add detailed instructions here if you want a custom fix -->
+
+
+---
+
+## Summary
+
+- Total: {N}
+- Fixable: {N}
+- Questions: {N}
+- Manual Review: {N}
+
+**Next Steps:**
+1. Edit this file to mark which findings to fix
+2. Run: `/review-code apply`

package/src/templates/workflow/REVIEW-SUMMARY.md

@@ -0,0 +1,35 @@
+# Code Review Summary
+
+**Reviewed:** {scope}
+**Timestamp:** {ISO-timestamp}
+**User Decisions:** {summary of user choices}
+
+## Summary
+
+- **Total Issues:** {N}
+- **Applied with User Approval:** {N}
+- **User-Resolved Questions:** {N}
+- **Manual Review Needed:** {N}
+- **Skipped by User:** {N}
+
+## Applied Fixes (User Approved)
+
+- `{file-path}:{line}` - {description of fix}
+- `{file-path}:{line}` - {description of fix}
+
+## User-Resolved Questions
+
+- `{file-path}:{line}` - {description} (user answered: {answer})
+
+## Manual Review Needed
+
+- `{file-path}:{line}` - {description}
+
+## Skipped Issues
+
+- `{file-path}:{line}` - User chose not to apply
+
+## Files Modified
+
+- {file-path} ({N} fixes applied)
+- {file-path} ({N} fixes applied)

package/src/templates/workflow/STATE.json

@@ -0,0 +1,9 @@
+{
+  "ticket": "{TICKET-ID}",
+  "feature": "{feature-name}",
+  "status": "in-progress",
+  "currentStep": 1,
+  "completed": [],
+  "failed": [],
+  "startedAt": "{ISO-timestamp}"
+}

package/src/templates/workflow/VERIFICATION-REPORT.md

@@ -0,0 +1,95 @@
+# Verification Report: {TICKET-ID}
+
+**Feature:** {feature-name}
+**Status:** PASSED | PARTIAL | FAILED
+**Verified:** {timestamp}
+
+---
+
+## Layer 1: Infrastructure
+
+### Files
+
+- [x] {path} — exists
+- [ ] {path} — MISSING
+
+**Result:** {N}/{M} files exist
+
+### Build
+
+**Command:** `{build-command}`
+**Status:** SUCCESS | FAILED
+
+{build errors if any}
+
+### Tests
+
+**Command:** `{test-command}`
+**Status:** SUCCESS | FAILED
+**Total:** {N} | **Passed:** {N} | **Failed:** {N}
+
+{test failure details if any}
+
+**Layer 1 Result:** PASSED | FAILED
+
+---
+
+## Layer 2: Feature Completeness
+
+{If feature.md was not found: "Skipped — no feature.md available (normal for quick-implement workflows)"}
+
+### Acceptance Criteria
+
+| # | Criterion | Status | Evidence |
+|---|-----------|--------|----------|
+| 1 | {criterion text} | SATISFIED | {file:line} |
+| 2 | {criterion text} | NOT SATISFIED | — |
+
+**Result:** {N}/{M} criteria satisfied
+
+### Functional Requirements
+
+| # | Requirement | Status | Evidence |
+|---|-------------|--------|----------|
+| 1 | {requirement text} | IMPLEMENTED | {file:line} |
+| 2 | {requirement text} | NOT IMPLEMENTED | — |
+
+**Result:** {N}/{M} requirements implemented
+
+### Component Completeness
+
+| Component | File | Status | Notes |
+|-----------|------|--------|-------|
+| {name} | {path} | COMPLETE | — |
+| {name} | {path} | PARTIAL | {what's missing} |
+
+**Result:** {N}/{M} components complete
+
+**Layer 2 Result:** PASSED | PARTIAL | SKIPPED
+
+---
+
+## Layer 3: Quality
+
+### Test Coverage for New Files
+
+| New File | Test File | Status |
+|----------|-----------|--------|
+| {src/path/File.ts} | {src/path/File.test.ts} | HAS TEST |
+| {src/path/Other.ts} | — | NO TEST |
+
+**Result:** {N}/{M} new files have tests
+
+**Layer 3 Result:** PASSED | PARTIAL
+
+---
+
+## Summary
+
+| Layer | Result | Details |
+|-------|--------|---------|
+| Infrastructure | PASSED / FAILED | {N}/{M} files, build {status}, tests {status} |
+| Feature Completeness | PASSED / PARTIAL / SKIPPED | {N}/{M} criteria, {N}/{M} requirements |
+| Quality | PASSED / PARTIAL | {N}/{M} new files have tests |
+
+**Overall:** PASSED | PARTIAL | FAILED

package/src/agents/integration-agent.md

@@ -1,220 +0,0 @@
----
-name: integration-agent
-description: Integrates new components into the application by following existing project patterns. Wires components, registers endpoints/routes, and runs final build and tests. Runs in forked context.
-tools: Read, Edit, Bash, Glob, Grep, Skill, mcp__jetbrains__get_file_problems, mcp__jetbrains__rename_refactoring
-model: sonnet
-color: blue
----
-
-# Integration Agent
-
-## Purpose
-
-Handles the integration step - wiring new components into the application by discovering and following existing project patterns. Registers routes/endpoints, wires dependencies, and runs final build and tests. Spawned by `implement-feature` command via the Task tool.
-
-## Input Contract
-
-The spawning command provides:
-
-```
-Feature Name: {feature-name}
-Components to Wire:
-- component: {ComponentName}
-  type: {component-type}
-  file: {path/to/component}
-  integration: {where it needs to be registered}
-Routes/Endpoints to Register:
-- route: {RouteName}
-  path: {/path}
-  file: {path/to/route-file}
-  registration: {where routes are registered}
-Integration Config:
-  Read from: .claude/.5/config.json
-  Patterns: {how components are typically integrated in this project}
-Affected Modules:
-- {module-path-1}
-- {module-path-2}
-```
-
-## Process
-
-### 1. Discover Integration Patterns
-
-First, understand how the project integrates components:
-
-1. **Read integration config** from `.claude/.5/config.json`:
-   - Where are routes/endpoints registered?
-   - How are services/components wired?
-   - What files need to be updated?
-
-2. **Explore existing patterns** if config is incomplete:
-   - Use Grep to find similar component registrations
-   - Read files where integration happens
-   - Identify the pattern used
-
-**Example patterns by framework:**
-- **Express.js**: Routes registered in `app.ts` or `routes/index.ts`
-- **Next.js**: API routes are file-based in `pages/api/` or `app/api/`
-- **NestJS**: Modules imported in `app.module.ts`
-- **Spring Boot**: Components auto-discovered via annotations
-- **FastAPI**: Routes registered in main app file
-- **Rails**: Routes in `config/routes.rb`
-
-### 2. Integrate Components
-
-For each component that needs integration:
-
-1. **Read the integration point file** (e.g., main app file, router file, module file)
-2. **Identify the existing pattern** by examining similar registrations
-3. **Add the new component** following the exact same pattern
-
-**Use Edit tool for precise insertions:**
-- Add import/require statements for new components
-- Add registration code following project conventions
-- Match existing code style (indentation, ordering, grouping)
-
-**Examples:**
-
-**Express.js pattern:**
-```javascript
-// Add import
-import { userRoutes } from './routes/user.routes';
-
-// Add route registration
-app.use('/api/users', userRoutes);
-```
-
-**NestJS pattern:**
-```typescript
-// Add import
-import { UserModule } from './user/user.module';
-
-// Add to imports array
-@Module({
-  imports: [UserModule, ...],
-})
-```
-
-**FastAPI pattern:**
-```python
-# Add import
-from routers import user_router
-
-# Add route registration
-app.include_router(user_router, prefix="/api/users")
-```
-
-### 3. Register Routes/Endpoints
-
-For each route/endpoint:
-
-1. **Read the routing configuration file** (specified in config or discovered)
-2. **Follow the existing pattern** for route registration
-3. **Add the new routes** maintaining consistency with existing routes
-
-### 4. Run Full Build
-
-Run the project build using the configured build skill or command:
-
-**If build skill is available:**
-```
-Skill tool call:
-  skill: "build-project"
-  args: "target=compile"
-```
-
-**If no build skill, use config command:**
-```bash
-{config.build.command from .claude/.5/config.json}
-```
-
-Parse the output to extract:
-- Build status (success/failed)
-- Error details if build fails
-- Duration
-
-### 5. Run Tests
-
-Execute tests using the configured test skill or command:
-
-**If test skill is available:**
-```
-Skill tool call:
-  skill: "run-tests"
-  args: "target=all"
-```
-
-**If no test skill, use config command:**
-```bash
-{config.build.testCommand from .claude/.5/config.json}
-```
-
-Parse the output to extract:
-- Total tests
-- Passed
-- Failed
-- Skipped
-- Error details for failures
-
-## Output Contract
-
-Return a structured result:
-
-```
-Integration Results:
-Status: success | failed
-
-Component Integration:
-- component: {ComponentName}
-  file: {integration file path}
-  status: integrated | failed
-  error: {if failed}
-
-Route Registration:
-- route: {RouteName}
-  file: {routing file path}
-  status: registered | failed
-  error: {if failed}
-
-Build:
-  status: success | failed
-  errors: |
-    {error output if failed}
-
-Tests:
-  status: passed | failed
-  total: {N}
-  passed: {N}
-  failed: {N}
-  skipped: {N}
-  failures:
-  - test: {testName}
-    error: {error message}
-
-Modified Files:
-- {path/to/modified/file1}
-- {path/to/modified/file2}
-
-File Problems:
-- file: {path}
-  errors: [{message}]
-  warnings: [{message}]
-```
-
-## Error Handling
-
-- If integration pattern cannot be identified, return failed with descriptive error
-- If build fails after integration, include full error output for diagnosis
-- If tests fail, include test names and error details
-- Do not attempt to fix errors - return them for the parent command to handle
-- If no integration is needed (e.g., file-based routing like Next.js), note this and proceed to build/test
-
-## DO NOT
-
-- DO NOT create new files (only modify existing integration points)
-- DO NOT update the state file (parent handles state)
-- DO NOT interact with the user (parent handles user interaction)
-- DO NOT guess at patterns - read config and existing code to match patterns exactly
-- DO NOT skip build or test steps (unless config explicitly disables them)
-- DO NOT modify files beyond what is needed for integration
-- DO NOT assume a specific framework - detect from config and codebase