@sienklogic/plan-build-run 2.0.0 → 2.0.1

package/plugins/pbr/templates/SUMMARY.md.tmpl

@@ -1,81 +1,81 @@
-# SUMMARY.md Template
-
-> Referenced by: executor agent, build skill, review skill
-> Do not edit this template during execution — copy the structure into your output.
-
-## Frontmatter (YAML)
-
-```yaml
----
-phase: "{phase_id}"
-plan: "{plan_id}"
-status: "complete"           # complete | partial | checkpoint
-subsystem: "{main subsystem affected}"
-tags:
-  - "{tag1}"
-  - "{tag2}"
-requires:                    # What this plan needs from other plans
-  - "{plan_id}: {artifact}"
-provides:                    # What this plan produces for other plans
-  - "{export/artifact description}"
-affects:
-  - "{affected area 1}"
-  - "{affected area 2}"
-tech_stack:
-  - "{technology used}"
-key_files:
-  - "{file1}: {what it does}"
-  - "{file2}: {what it does}"
-key_decisions:
-  - "{decision 1}: {rationale}"
-patterns:
-  - "{pattern used}: {where}"
-metrics:
-  duration_minutes: {n}
-  tasks_completed: {n}
-  tasks_total: {n}
-  commits: {n}
-  files_created: {n}
-  files_modified: {n}
-deferred:
-  - "{thing noticed but not implemented}"
-self_check_failures:         # Only present if self-check found issues
-  - "{failure description}"
----
-```
-
-## Body Structure
-
-```markdown
-# Plan Summary: {plan_id}
-
-## What Was Built
-
-{2-3 paragraph description of what was accomplished}
-
-## Task Results
-
-| Task | Status | Commit | Files | Verify |
-|------|--------|--------|-------|--------|
-| {task_id}: {name} | done | {hash} | {count} | passed |
-
-## Key Implementation Details
-
-{Important details about HOW things were implemented that future plans need to know}
-
-## Known Issues
-
-{Any issues discovered during execution that weren't blockers but should be tracked}
-
-## Dependencies Provided
-
-{What other plans can now depend on — exports, files, APIs created}
-```
-
-## Status Values
-
-| Status | Meaning |
-|--------|---------|
-| `complete` | All tasks completed successfully |
-| `partial` | Some tasks completed, execution stopped |
-| `checkpoint` | Execution paused at a checkpoint task, waiting for human |
+# SUMMARY.md Template
+
+> Referenced by: executor agent, build skill, review skill
+> Do not edit this template during execution — copy the structure into your output.
+
+## Frontmatter (YAML)
+
+```yaml
+---
+phase: "{phase_id}"
+plan: "{plan_id}"
+status: "complete"           # complete | partial | checkpoint
+subsystem: "{main subsystem affected}"
+tags:
+  - "{tag1}"
+  - "{tag2}"
+requires:                    # What this plan needs from other plans
+  - "{plan_id}: {artifact}"
+provides:                    # What this plan produces for other plans
+  - "{export/artifact description}"
+affects:
+  - "{affected area 1}"
+  - "{affected area 2}"
+tech_stack:
+  - "{technology used}"
+key_files:
+  - "{file1}: {what it does}"
+  - "{file2}: {what it does}"
+key_decisions:
+  - "{decision 1}: {rationale}"
+patterns:
+  - "{pattern used}: {where}"
+metrics:
+  duration_minutes: {n}
+  tasks_completed: {n}
+  tasks_total: {n}
+  commits: {n}
+  files_created: {n}
+  files_modified: {n}
+deferred:
+  - "{thing noticed but not implemented}"
+self_check_failures:         # Only present if self-check found issues
+  - "{failure description}"
+---
+```
+
+## Body Structure
+
+```markdown
+# Plan Summary: {plan_id}
+
+## What Was Built
+
+{2-3 paragraph description of what was accomplished}
+
+## Task Results
+
+| Task | Status | Commit | Files | Verify |
+|------|--------|--------|-------|--------|
+| {task_id}: {name} | done | {hash} | {count} | passed |
+
+## Key Implementation Details
+
+{Important details about HOW things were implemented that future plans need to know}
+
+## Known Issues
+
+{Any issues discovered during execution that weren't blockers but should be tracked}
+
+## Dependencies Provided
+
+{What other plans can now depend on — exports, files, APIs created}
+```
+
+## Status Values
+
+| Status | Meaning |
+|--------|---------|
+| `complete` | All tasks completed successfully |
+| `partial` | Some tasks completed, execution stopped |
+| `checkpoint` | Execution paused at a checkpoint task, waiting for human |

package/plugins/pbr/templates/VERIFICATION-DETAIL.md.tmpl

@@ -1,116 +1,116 @@
-<!-- Source: agents/verifier.md | Purpose: Detailed output format for verification reports produced by the verifier agent -->
-
-```yaml
----
-phase: "{phase_id}"
-verified: "{ISO timestamp}"
-status: "passed"           # passed | gaps_found | human_needed
-is_re_verification: false  # true if re-verifying after gap closure
-score:
-  total_must_haves: {n}
-  verified: {n}
-  failed: {n}
-  partial: {n}
-  human_needed: {n}
-gaps:
-  - must_have: "{description of the failed must-have}"
-    level: "{existence | substantive | wired}"
-    evidence: "{what you found}"
-    recommendation: "{specific action to fix}"
-anti_patterns:
-  todos: {count}
-  stubs: {count}
-  console_logs: {count}
-  skipped_tests: {count}
-  hardcoded_secrets: {count}
----
-
-# Phase Verification: {phase_name}
-
-> Verified: {date}
-> Status: **{STATUS}**
-> Score: {verified}/{total} must-haves verified
-> Re-verification: {yes/no}
-
-## Observable Truths
-
-| # | Truth | Status | Evidence |
-|---|-------|--------|----------|
-| 1 | {truth statement} | VERIFIED | {evidence summary with file paths and line numbers} |
-| 2 | {truth statement} | FAILED | {what's wrong, what was expected, what was found} |
-| 3 | {truth statement} | HUMAN_NEEDED | {why it can't be verified programmatically} |
-
-## Artifact Verification
-
-| # | Artifact | L1: Exists | L2: Substantive | L3: Wired | Status |
-|---|----------|-----------|-----------------|-----------|--------|
-| 1 | `{file/export}` | YES | YES (142 lines, real logic) | WIRED (imported by 3 files) | PASS |
-| 2 | `{file/export}` | YES | STUB (TODO at L42, empty handler L67) | N/A | FAIL |
-| 3 | `{file/export}` | YES | YES | ORPHANED (not imported anywhere) | FAIL |
-| 4 | `{file/export}` | NO | N/A | N/A | FAIL |
-
-## Key Link Verification
-
-| # | Link Description | Source | Target | Status | Evidence |
-|---|-----------------|--------|--------|--------|----------|
-| 1 | {what connects to what} | `{source_file}` | `{target_file}` | WIRED | Import at L12, called at L45 |
-| 2 | {what connects to what} | `{source_file}` | `{target_file}` | BROKEN | Imported but never called |
-
-## Gaps Found
-
-{Only present if status is gaps_found}
-
-### Gap 1: {Short description}
-
-- **Must-Have**: {which must-have this gap blocks}
-- **Level Failed**: {existence / substantive / wired}
-- **Evidence**: {specific evidence — file paths, line numbers, command output}
-- **Impact**: {what doesn't work because of this gap}
-- **Recommendation**: {specific action to close this gap}
-
-### Gap 2: {Short description}
-...
-
-## Human Verification Items
-
-{Only present if there are items requiring human verification}
-
-### Item 1: {What needs checking}
-
-- **Must-Have**: {which must-have this relates to}
-- **Why Manual**: {why it can't be verified automatically}
-- **How to Test**: {step-by-step instructions}
-- **Expected Result**: {what success looks like}
-
-## Anti-Pattern Scan
-
-| Pattern | Count | Severity | Files |
-|---------|-------|----------|-------|
-| TODO/FIXME comments | {n} | {low/medium/high} | {file list} |
-| Stub implementations | {n} | {high} | {file list} |
-| Console.log in production | {n} | {low} | {file list} |
-| Skipped tests | {n} | {medium} | {file list} |
-| Hardcoded secrets | {n} | {critical} | {file list} |
-| Empty catch blocks | {n} | {medium} | {file list} |
-
-## Regressions
-
-{Only present in re-verification mode}
-
-| # | Must-Have | Previous Status | Current Status | Evidence |
-|---|----------|----------------|----------------|----------|
-| 1 | {must-have} | VERIFIED | FAILED | {what changed} |
-
-## Summary
-
-### Phase Health
-- **Must-haves**: {n}/{total} verified ({percentage}%)
-- **Gaps**: {n} blocking, {n} non-blocking
-- **Anti-patterns**: {n} total ({n} critical)
-- **Human items**: {n} pending
-
-### Recommendations
-1. {Most important action to take}
-2. {Second most important}
-3. ...
-```
+<!-- Source: agents/verifier.md | Purpose: Detailed output format for verification reports produced by the verifier agent -->
+
+```yaml
+---
+phase: "{phase_id}"
+verified: "{ISO timestamp}"
+status: "passed"           # passed | gaps_found | human_needed
+is_re_verification: false  # true if re-verifying after gap closure
+score:
+  total_must_haves: {n}
+  verified: {n}
+  failed: {n}
+  partial: {n}
+  human_needed: {n}
+gaps:
+  - must_have: "{description of the failed must-have}"
+    level: "{existence | substantive | wired}"
+    evidence: "{what you found}"
+    recommendation: "{specific action to fix}"
+anti_patterns:
+  todos: {count}
+  stubs: {count}
+  console_logs: {count}
+  skipped_tests: {count}
+  hardcoded_secrets: {count}
+---
+
+# Phase Verification: {phase_name}
+
+> Verified: {date}
+> Status: **{STATUS}**
+> Score: {verified}/{total} must-haves verified
+> Re-verification: {yes/no}
+
+## Observable Truths
+
+| # | Truth | Status | Evidence |
+|---|-------|--------|----------|
+| 1 | {truth statement} | VERIFIED | {evidence summary with file paths and line numbers} |
+| 2 | {truth statement} | FAILED | {what's wrong, what was expected, what was found} |
+| 3 | {truth statement} | HUMAN_NEEDED | {why it can't be verified programmatically} |
+
+## Artifact Verification
+
+| # | Artifact | L1: Exists | L2: Substantive | L3: Wired | Status |
+|---|----------|-----------|-----------------|-----------|--------|
+| 1 | `{file/export}` | YES | YES (142 lines, real logic) | WIRED (imported by 3 files) | PASS |
+| 2 | `{file/export}` | YES | STUB (TODO at L42, empty handler L67) | N/A | FAIL |
+| 3 | `{file/export}` | YES | YES | ORPHANED (not imported anywhere) | FAIL |
+| 4 | `{file/export}` | NO | N/A | N/A | FAIL |
+
+## Key Link Verification
+
+| # | Link Description | Source | Target | Status | Evidence |
+|---|-----------------|--------|--------|--------|----------|
+| 1 | {what connects to what} | `{source_file}` | `{target_file}` | WIRED | Import at L12, called at L45 |
+| 2 | {what connects to what} | `{source_file}` | `{target_file}` | BROKEN | Imported but never called |
+
+## Gaps Found
+
+{Only present if status is gaps_found}
+
+### Gap 1: {Short description}
+
+- **Must-Have**: {which must-have this gap blocks}
+- **Level Failed**: {existence / substantive / wired}
+- **Evidence**: {specific evidence — file paths, line numbers, command output}
+- **Impact**: {what doesn't work because of this gap}
+- **Recommendation**: {specific action to close this gap}
+
+### Gap 2: {Short description}
+...
+
+## Human Verification Items
+
+{Only present if there are items requiring human verification}
+
+### Item 1: {What needs checking}
+
+- **Must-Have**: {which must-have this relates to}
+- **Why Manual**: {why it can't be verified automatically}
+- **How to Test**: {step-by-step instructions}
+- **Expected Result**: {what success looks like}
+
+## Anti-Pattern Scan
+
+| Pattern | Count | Severity | Files |
+|---------|-------|----------|-------|
+| TODO/FIXME comments | {n} | {low/medium/high} | {file list} |
+| Stub implementations | {n} | {high} | {file list} |
+| Console.log in production | {n} | {low} | {file list} |
+| Skipped tests | {n} | {medium} | {file list} |
+| Hardcoded secrets | {n} | {critical} | {file list} |
+| Empty catch blocks | {n} | {medium} | {file list} |
+
+## Regressions
+
+{Only present in re-verification mode}
+
+| # | Must-Have | Previous Status | Current Status | Evidence |
+|---|----------|----------------|----------------|----------|
+| 1 | {must-have} | VERIFIED | FAILED | {what changed} |
+
+## Summary
+
+### Phase Health
+- **Must-haves**: {n}/{total} verified ({percentage}%)
+- **Gaps**: {n} blocking, {n} non-blocking
+- **Anti-patterns**: {n} total ({n} critical)
+- **Human items**: {n} pending
+
+### Recommendations
+1. {Most important action to take}
+2. {Second most important}
+3. ...
+```

package/plugins/pbr/templates/codebase/ARCHITECTURE.md.tmpl

@@ -1,98 +1,98 @@
-<!-- Source: agents/codebase-mapper.md | Purpose: Output format for ARCHITECTURE.md codebase analysis -->
-# Architecture
-
-> Analyzed: {date}
-> Pattern: {MVC / Layered / Hexagonal / Microservices / Monolith / etc.}
-
-## Pattern Overview
-
-{2-3 paragraphs describing the overall architectural pattern with evidence from the codebase}
-
-**Evidence**: {file paths, import patterns, directory structure that support this classification}
-
-## Layers
-
-| Layer | Purpose | Directory | Key Files |
-|-------|---------|-----------|-----------|
-| {Presentation} | {UI rendering} | {src/components/} | {App.tsx, Layout.tsx} |
-| {API/Routes} | {HTTP handling} | {src/routes/ or src/app/api/} | {users.ts, auth.ts} |
-| {Business Logic} | {Core domain} | {src/services/} | {UserService.ts} |
-| {Data Access} | {Database interaction} | {src/repositories/ or src/db/} | {UserRepo.ts} |
-| {Infrastructure} | {External services} | {src/lib/ or src/integrations/} | {email.ts, storage.ts} |
-
-### Layer Rules
-
-{How layers communicate — what imports what? What are the dependency rules?}
-
-```
-Presentation → API → Business → Data Access → Database
-                ↓
-            Infrastructure
-```
-
-## Data Flow
-
-### Request Lifecycle
-
-{How a typical request flows through the system}
-
-```
-1. Client sends request
-2. → {Router/Framework} routes to handler
-3. → {Middleware} runs (auth, validation, logging)
-4. → {Controller/Handler} processes request
-5. → {Service} executes business logic
-6. → {Repository/Model} queries database
-7. → Response returns through the stack
-```
-
-### State Management
-
-| Context | Approach | Implementation | Files |
-|---------|----------|---------------|-------|
-| Client state | {Redux / Zustand / Context / etc.} | {how it's structured} | {store files} |
-| Server state | {React Query / SWR / etc.} | {how it's used} | {hook files} |
-| Session state | {JWT / cookies / etc.} | {how it's managed} | {auth files} |
-
-## Key Abstractions
-
-| Abstraction | Purpose | Implementation | Used By |
-|-------------|---------|---------------|---------|
-| {Repository} | {Database access} | {Abstract class + implementations} | {Services} |
-| {Middleware} | {Cross-cutting concerns} | {Function signature} | {Routes} |
-| {DTO/Schema} | {Data validation} | {Zod schemas / class-validator} | {Routes, Services} |
-
-## Entry Points
-
-| Type | File | Config | Notes |
-|------|------|--------|-------|
-| Web app | {src/app/page.tsx} | {port 3000} | {Next.js App Router} |
-| API server | {src/server.ts} | {port 8080} | {Express server} |
-| CLI | {src/cli.ts} | - | {Commander.js} |
-| Workers | {src/workers/} | {queue config} | {Bull/BullMQ} |
-| Cron | {src/cron/} | {schedule} | {node-cron} |
-
-## Error Handling Strategy
-
-| Layer | Pattern | Implementation |
-|-------|---------|---------------|
-| API | {Error middleware + HTTP status codes} | {src/middleware/error.ts} |
-| Service | {Custom error classes} | {src/errors/} |
-| Client | {Error boundaries + toast notifications} | {src/components/ErrorBoundary.tsx} |
-
-### Error Flow
-
-```
-Service throws AppError → Controller catches → Error middleware formats response → Client displays
-```
-
-## Security Architecture
-
-| Aspect | Implementation | Files |
-|--------|---------------|-------|
-| Authentication | {how auth works} | {files} |
-| Authorization | {RBAC / ABAC / etc.} | {files} |
-| Input validation | {where and how} | {files} |
-| CORS | {configuration} | {files} |
-| Rate limiting | {if present} | {files} |
-| CSRF protection | {if present} | {files} |
+<!-- Source: agents/codebase-mapper.md | Purpose: Output format for ARCHITECTURE.md codebase analysis -->
+# Architecture
+
+> Analyzed: {date}
+> Pattern: {MVC / Layered / Hexagonal / Microservices / Monolith / etc.}
+
+## Pattern Overview
+
+{2-3 paragraphs describing the overall architectural pattern with evidence from the codebase}
+
+**Evidence**: {file paths, import patterns, directory structure that support this classification}
+
+## Layers
+
+| Layer | Purpose | Directory | Key Files |
+|-------|---------|-----------|-----------|
+| {Presentation} | {UI rendering} | {src/components/} | {App.tsx, Layout.tsx} |
+| {API/Routes} | {HTTP handling} | {src/routes/ or src/app/api/} | {users.ts, auth.ts} |
+| {Business Logic} | {Core domain} | {src/services/} | {UserService.ts} |
+| {Data Access} | {Database interaction} | {src/repositories/ or src/db/} | {UserRepo.ts} |
+| {Infrastructure} | {External services} | {src/lib/ or src/integrations/} | {email.ts, storage.ts} |
+
+### Layer Rules
+
+{How layers communicate — what imports what? What are the dependency rules?}
+
+```
+Presentation → API → Business → Data Access → Database
+                ↓
+            Infrastructure
+```
+
+## Data Flow
+
+### Request Lifecycle
+
+{How a typical request flows through the system}
+
+```
+1. Client sends request
+2. → {Router/Framework} routes to handler
+3. → {Middleware} runs (auth, validation, logging)
+4. → {Controller/Handler} processes request
+5. → {Service} executes business logic
+6. → {Repository/Model} queries database
+7. → Response returns through the stack
+```
+
+### State Management
+
+| Context | Approach | Implementation | Files |
+|---------|----------|---------------|-------|
+| Client state | {Redux / Zustand / Context / etc.} | {how it's structured} | {store files} |
+| Server state | {React Query / SWR / etc.} | {how it's used} | {hook files} |
+| Session state | {JWT / cookies / etc.} | {how it's managed} | {auth files} |
+
+## Key Abstractions
+
+| Abstraction | Purpose | Implementation | Used By |
+|-------------|---------|---------------|---------|
+| {Repository} | {Database access} | {Abstract class + implementations} | {Services} |
+| {Middleware} | {Cross-cutting concerns} | {Function signature} | {Routes} |
+| {DTO/Schema} | {Data validation} | {Zod schemas / class-validator} | {Routes, Services} |
+
+## Entry Points
+
+| Type | File | Config | Notes |
+|------|------|--------|-------|
+| Web app | {src/app/page.tsx} | {port 3000} | {Next.js App Router} |
+| API server | {src/server.ts} | {port 8080} | {Express server} |
+| CLI | {src/cli.ts} | - | {Commander.js} |
+| Workers | {src/workers/} | {queue config} | {Bull/BullMQ} |
+| Cron | {src/cron/} | {schedule} | {node-cron} |
+
+## Error Handling Strategy
+
+| Layer | Pattern | Implementation |
+|-------|---------|---------------|
+| API | {Error middleware + HTTP status codes} | {src/middleware/error.ts} |
+| Service | {Custom error classes} | {src/errors/} |
+| Client | {Error boundaries + toast notifications} | {src/components/ErrorBoundary.tsx} |
+
+### Error Flow
+
+```
+Service throws AppError → Controller catches → Error middleware formats response → Client displays
+```
+
+## Security Architecture
+
+| Aspect | Implementation | Files |
+|--------|---------------|-------|
+| Authentication | {how auth works} | {files} |
+| Authorization | {RBAC / ABAC / etc.} | {files} |
+| Input validation | {where and how} | {files} |
+| CORS | {configuration} | {files} |
+| Rate limiting | {if present} | {files} |
+| CSRF protection | {if present} | {files} |