prizmkit 1.0.0 → 1.0.1

package/bundled/dev-pipeline/templates/bootstrap-prompt.md

@@ -0,0 +1,262 @@
+# Dev-Pipeline Session Bootstrap
+
+## Session Context
+
+- **Pipeline Run ID**: {{RUN_ID}}
+- **Session ID**: {{SESSION_ID}}
+- **Feature ID**: {{FEATURE_ID}}
+- **Feature Title**: {{FEATURE_TITLE}}
+- **Feature Slug**: {{FEATURE_SLUG}}
+- **Complexity**: {{COMPLEXITY}} (mode: {{PIPELINE_MODE}})
+- **Retry Count**: {{RETRY_COUNT}} / {{MAX_RETRIES}}
+- **Previous Session Status**: {{PREV_SESSION_STATUS}}
+- **Resume From Phase**: {{RESUME_PHASE}}
+- **Init Status**: {{INIT_DONE}} | Artifacts: spec={{HAS_SPEC}} plan={{HAS_PLAN}} tasks={{HAS_TASKS}}
+
+## Your Mission
+
+You are the **session orchestrator**. Implement Feature {{FEATURE_ID}}: "{{FEATURE_TITLE}}".
+
+**CRITICAL SESSION LIFECYCLE RULE**: You are the main session process. You MUST NOT exit until ALL work is complete and session-status.json is written. When you spawn subagents, you MUST **wait for each to finish** (run_in_background=false) before proceeding. Do NOT spawn an agent in the background and exit — that kills the session.
+
+**MANDATORY TEAM REQUIREMENT**: You MUST use the `prizm-dev-team` multi-agent team to complete this feature. This is NON-NEGOTIABLE. You are FORBIDDEN from implementing the feature as a single agent — all work MUST be distributed through the prizm-dev-team members (PM, Dev, Reviewer). Specifically:
+1. You MUST ensure a prizm-dev-team is available before starting any phase (see Step 1 below for reuse-or-create logic)
+2. You MUST spawn PM, Dev, and Reviewer agents using the `Task` tool with `team_name` and `subagent_type` parameters
+3. Every implementation, planning, and review phase MUST be executed by the appropriate team agent — NOT by you directly
+4. If you attempt to do the work yourself without spawning team agents, the session is considered FAILED
+
+### Team Definition Reference
+
+The prizm-dev-team definition is maintained in the project at:
+- **Source of truth**: `core/team/prizm-dev-team.json`
+- **Installed team config (current platform)**: `{{TEAM_CONFIG_PATH}}`
+  - CodeBuddy: `~/.codebuddy/teams/prizm-dev-team/config.json` — full team config with members, may support reuse
+  - Claude Code: `.claude/team-info.json` — reference only (no native team system; agents are in `.claude/agents/`)
+
+When creating a new team, use these files as reference for team member names, roles, agentTypes, and prompts.
+
+### Feature Description
+
+{{FEATURE_DESCRIPTION}}
+
+### Acceptance Criteria
+
+{{ACCEPTANCE_CRITERIA}}
+
+### Dependencies (Already Completed)
+
+{{COMPLETED_DEPENDENCIES}}
+
+### App Global Context
+
+{{GLOBAL_CONTEXT}}
+
+## PrizmKit Directory Convention
+
+**ALWAYS** use per-feature subdirectory `.prizmkit/specs/{{FEATURE_SLUG}}/`:
+
+```
+.prizmkit/specs/{{FEATURE_SLUG}}/spec.md
+.prizmkit/specs/{{FEATURE_SLUG}}/plan.md
+.prizmkit/specs/{{FEATURE_SLUG}}/tasks.md
+.prizmkit/specs/REGISTRY.md
+```
+
+## Execution Instructions
+
+**YOU are the orchestrator. Do NOT delegate to a Coordinator agent. Execute each phase yourself by spawning the appropriate team agent with run_in_background=false and waiting for its result.**
+
+**TEAM ENFORCEMENT**: Every phase below that mentions spawning a PM/Dev/Reviewer agent MUST use the `Task` tool with the active team's `team_name`. You MUST NOT skip the team setup step or attempt to perform PM/Dev/Reviewer work yourself. Violation of this rule constitutes a session failure.
+
+### Step 1: Initialize
+
+#### Team Setup: Reuse or Create
+
+Different AI CLI platforms have different team lifecycle behaviors. Some support reusing an existing team across sessions; others require creating a new team every time.
+
+**Follow this logic to determine team availability:**
+
+1. **Check if a team already exists and can be reused**:
+   - Read the team config file at `{{TEAM_CONFIG_PATH}}`
+   - If it exists and is valid (has members with correct agentTypes like `prizm-dev-team-pm`, `prizm-dev-team-dev`, `prizm-dev-team-reviewer`), try to reuse it
+   - Set `TEAM_REUSED=true` and record the `team_name` from the config
+
+2. **If no reusable team exists, create a new one**:
+   - Reference the team definition at `core/team/prizm-dev-team.json` (source of truth for member roles and prompts)
+   - Call `TeamCreate` with `team_name="prizm-dev-team-{{FEATURE_ID}}"` and `description="Implementing {{FEATURE_TITLE}}"`
+   - Set `TEAM_REUSED=false`
+
+3. **Record which path was taken** — this determines whether `TeamDelete` is needed at the end (only delete if you created; do NOT delete a reused team)
+
+{{IF_FRESH_START}}
+#### Initialize dev-team directories
+
+```bash
+python3 {{INIT_SCRIPT_PATH}} --project-root {{PROJECT_ROOT}} --feature-id {{FEATURE_ID}} --feature-slug {{FEATURE_SLUG}}
+```
+{{END_IF_FRESH_START}}
+
+{{IF_RESUME}}
+#### Resume Context
+
+This is a **resume** from Phase {{RESUME_PHASE}}. After completing the team setup above:
+1. Read artifacts in `.prizmkit/specs/{{FEATURE_SLUG}}/` (spec.md, plan.md, tasks.md)
+2. Resume the pipeline from Phase {{RESUME_PHASE}} below
+{{END_IF_RESUME}}
+
+### Step 2: Pipeline Phases
+
+{{IF_INIT_NEEDED}}
+#### Phase 0: Project Bootstrap
+- Run `prizmkit.init` (invoke the prizmkit-init skill)
+- Run `python3 {{INIT_SCRIPT_PATH}} --project-root {{PROJECT_ROOT}} --feature-id {{FEATURE_ID}} --feature-slug {{FEATURE_SLUG}}`
+- **CP-0**: Verify `.prizm-docs/root.prizm`, `.prizmkit/config.json` exist
+{{END_IF_INIT_NEEDED}}
+{{IF_INIT_DONE}}
+#### Phase 0: SKIP (already initialized)
+{{END_IF_INIT_DONE}}
+
+{{IF_MODE_LITE}}
+#### Phase 1-3: Lightweight Planning (combined)
+- Spawn PM agent (Task tool, subagent_type="prizm-dev-team-pm", run_in_background=false)
+  Prompt: "Read {{PM_SUBAGENT_PATH}}. For feature {{FEATURE_ID}} (slug: {{FEATURE_SLUG}}), create a CONCISE implementation plan. Write:
+  1. `.prizmkit/specs/{{FEATURE_SLUG}}/plan.md` — brief architecture (under 100 lines): key components, data flow, file structure
+  2. `.prizmkit/specs/{{FEATURE_SLUG}}/tasks.md` — task checklist with `[ ]` checkboxes, each task = one implementable unit
+  Do NOT generate spec.md. Keep it minimal."
+- **Wait for PM to return**
+- **CP-1**: plan.md and tasks.md exist
+
+#### Phase 4: SKIP (lite mode)
+{{END_IF_MODE_LITE}}
+
+{{IF_MODE_STANDARD}}
+#### Phase 1-3: Specify + Plan + Tasks (combined, one PM session)
+- Spawn PM agent (Task tool, subagent_type="prizm-dev-team-pm", run_in_background=false)
+  Prompt: "Read {{PM_SUBAGENT_PATH}}. For feature {{FEATURE_ID}} (slug: {{FEATURE_SLUG}}), complete all three planning steps in this single session:
+  1. Run prizmkit-specify → generate `.prizmkit/specs/{{FEATURE_SLUG}}/spec.md` (concise, under 150 lines)
+  2. Run prizmkit-plan → generate `.prizmkit/specs/{{FEATURE_SLUG}}/plan.md` (architecture, components, interface design, data model, testing strategy — all in one file)
+  3. Run prizmkit-tasks → generate `.prizmkit/specs/{{FEATURE_SLUG}}/tasks.md` with `[ ]` checkboxes
+  All three files go under `.prizmkit/specs/{{FEATURE_SLUG}}/`."
+- **Wait for PM to return**
+- **CP-1**: spec.md, plan.md, and tasks.md all exist
+
+#### Phase 4: Analyze (cross-check)
+- Spawn Reviewer agent (Task tool, subagent_type="prizm-dev-team-reviewer", run_in_background=false)
+  Prompt: "Read {{REVIEWER_SUBAGENT_PATH}}. Run prizmkit-analyze for feature {{FEATURE_ID}} (slug: {{FEATURE_SLUG}}). Cross-check `.prizmkit/specs/{{FEATURE_SLUG}}/spec.md`, `plan.md`, and `tasks.md` for consistency. Report any CRITICAL or HIGH issues."
+- **Wait for Reviewer to return**
+- If CRITICAL issues found: spawn PM to fix, then re-run analyze (max 1 round)
+- **CP-2**: No CRITICAL issues
+{{END_IF_MODE_STANDARD}}
+
+{{IF_MODE_FULL}}
+#### Phase 1-3: Specify + Plan + Tasks (combined, one PM session)
+- Spawn PM agent (Task tool, subagent_type="prizm-dev-team-pm", run_in_background=false)
+  Prompt: "Read {{PM_SUBAGENT_PATH}}. For feature {{FEATURE_ID}} (slug: {{FEATURE_SLUG}}), complete all three planning steps in this single session:
+  1. Run prizmkit-specify → generate `.prizmkit/specs/{{FEATURE_SLUG}}/spec.md`. If there are `[NEEDS CLARIFICATION]` markers, run prizmkit-clarify to resolve them.
+  2. Run prizmkit-plan → generate `.prizmkit/specs/{{FEATURE_SLUG}}/plan.md` (architecture, components, interface design, data model, testing strategy, risk assessment — all in one file)
+  3. Run prizmkit-tasks → generate `.prizmkit/specs/{{FEATURE_SLUG}}/tasks.md` with `[ ]` checkboxes
+  All three files go under `.prizmkit/specs/{{FEATURE_SLUG}}/`."
+- **Wait for PM to return**
+- **CP-1**: spec.md, plan.md, and tasks.md all exist
+
+#### Phase 4: Analyze (cross-check)
+- Spawn Reviewer agent (Task tool, subagent_type="prizm-dev-team-reviewer", run_in_background=false)
+  Prompt: "Read {{REVIEWER_SUBAGENT_PATH}}. Run prizmkit-analyze for feature {{FEATURE_ID}} (slug: {{FEATURE_SLUG}}). Cross-check `.prizmkit/specs/{{FEATURE_SLUG}}/spec.md`, `plan.md`, and `tasks.md` for consistency. Report any CRITICAL or HIGH issues."
+- **Wait for Reviewer to return**
+- If CRITICAL issues found: spawn PM to fix, then re-run analyze (max 1 round)
+- **CP-2**: No CRITICAL issues
+{{END_IF_MODE_FULL}}
+
+#### Phase 5: Schedule & Implement
+- Read tasks from `.prizmkit/specs/{{FEATURE_SLUG}}/tasks.md`
+- Create TaskList entries and assign to Dev agents
+- Spawn Dev agent (Task tool, subagent_type="prizm-dev-team-dev", run_in_background=false)
+  Prompt: "Read {{DEV_SUBAGENT_PATH}}. Implement all tasks for feature {{FEATURE_ID}} (slug: {{FEATURE_SLUG}}) using prizmkit-implement with TDD. Read the plan from `.prizmkit/specs/{{FEATURE_SLUG}}/plan.md` and tasks from `tasks.md`. Mark completed tasks [x] in tasks.md."
+- **Wait for Dev to return**
+- All tasks marked `[x]`, tests pass
+
+#### Phase 6: Review
+- Spawn Reviewer agent (Task tool, subagent_type="prizm-dev-team-reviewer", run_in_background=false)
+  Prompt: "Read {{REVIEWER_SUBAGENT_PATH}}. For feature {{FEATURE_ID}} (slug: {{FEATURE_SLUG}}):
+  1. Run prizmkit-code-review for spec compliance and code quality
+  2. Write and execute integration tests covering all user stories from spec.md
+  Report verdict: PASS, PASS_WITH_WARNINGS, or NEEDS_FIXES."
+- **Wait for Reviewer to return**
+- If NEEDS_FIXES: spawn Dev to fix, then re-run Review (max 3 rounds)
+- **CP-3**: Integration tests pass, review verdict is not NEEDS_FIXES
+
+#### Phase 7: Summarize & Commit — DO NOT SKIP
+
+**IMPORTANT**: Phase 7 is for **new feature** commits only. If this session is a bug fix to an existing feature, skip `prizmkit.summarize` (do NOT create new REGISTRY.md entries for bug fixes — bugs are refinements of incomplete features, not new functionality). Still run `prizmkit.committer` with `fix(<scope>):` prefix.
+
+**7a.** Run `prizmkit.summarize` (invoke the prizmkit-summarize skill) → archive to REGISTRY.md
+
+**7b.** Run `prizmkit.committer` (invoke the prizmkit-committer skill) → `feat({{FEATURE_ID}}): {{FEATURE_TITLE}}`, do NOT push
+
+### Step 3: Report Session Status
+
+**CRITICAL**: Before this session ends, you MUST write the session status file.
+
+Write to: `{{SESSION_STATUS_PATH}}`
+
+```json
+{
+  "session_id": "{{SESSION_ID}}",
+  "feature_id": "{{FEATURE_ID}}",
+  "feature_slug": "{{FEATURE_SLUG}}",
+  "status": "<success|partial|failed>",
+  "completed_phases": [0, 1, 2, 3, 4, 5, 6, 7],
+  "current_phase": 7,
+  "checkpoint_reached": "CP-3",
+  "tasks_completed": 12,
+  "tasks_total": 12,
+  "errors": [],
+  "can_resume": false,
+  "resume_from_phase": null,
+  "artifacts": {
+    "spec_path": ".prizmkit/specs/{{FEATURE_SLUG}}/spec.md",
+    "plan_path": ".prizmkit/specs/{{FEATURE_SLUG}}/plan.md",
+    "tasks_path": ".prizmkit/specs/{{FEATURE_SLUG}}/tasks.md"
+  },
+  "git_commit": "<commit hash if Phase 7 completed>",
+  "timestamp": "2026-03-04T10:00:00Z"
+}
+```
+
+**Status values**: `success` (all phases done) | `partial` (can resume) | `failed` (unrecoverable)
+
+If you encounter an error, still write session-status.json with status="failed" and error details.
+
+### Step 4: Team Cleanup (conditional)
+
+**Only if you CREATED the team in Step 1** (i.e. `TEAM_REUSED=false`), clean up:
+```
+TeamDelete
+```
+
+**If you REUSED an existing team** (i.e. `TEAM_REUSED=true`), do NOT call `TeamDelete` — the team is shared and may be used by other sessions.
+
+## Critical Paths
+
+| Resource | Path |
+|----------|------|
+| Team Definition (source of truth) | `core/team/prizm-dev-team.json` |
+| Team Config (installed) | `{{TEAM_CONFIG_PATH}}` |
+| Feature Artifacts Dir | `.prizmkit/specs/{{FEATURE_SLUG}}/` |
+| PM Agent Def | {{PM_SUBAGENT_PATH}} |
+| Dev Agent Def | {{DEV_SUBAGENT_PATH}} |
+| Reviewer Agent Def | {{REVIEWER_SUBAGENT_PATH}} |
+| Session Status Output | {{SESSION_STATUS_PATH}} |
+| Project Root | {{PROJECT_ROOT}} |
+
+## Reminders
+
+- **MANDATORY**: You MUST use `prizm-dev-team` (reuse existing or create new) — single-agent execution is FORBIDDEN
+- **Team definition source**: `core/team/prizm-dev-team.json`; installed at `{{TEAM_CONFIG_PATH}}`
+- **All artifacts go under `.prizmkit/specs/{{FEATURE_SLUG}}/`** — only 3 files: spec.md, plan.md, tasks.md
+- Dev agents use TDD approach
+- Phase 7 (summarize + commit) is MANDATORY
+- ALWAYS write session-status.json before exiting
+- **NEVER exit the session early** — wait for all spawned agents to complete
+- Do NOT use `run_in_background=true` when spawning agents
+- Only call `TeamDelete` if you created the team; do NOT delete a reused team

package/bundled/dev-pipeline/templates/bug-fix-list-schema.json

@@ -0,0 +1,159 @@
+{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "title": "Dev-Pipeline Bug Fix List",
+  "description": "Schema for bug-fix-list.json — standardized input for the Bug Fix Pipeline",
+  "type": "object",
+  "required": ["$schema", "project_name", "bugs"],
+  "properties": {
+    "$schema": {
+      "type": "string",
+      "const": "dev-pipeline-bug-fix-list-v1"
+    },
+    "project_name": {
+      "type": "string",
+      "minLength": 1
+    },
+    "project_description": {
+      "type": "string"
+    },
+    "created_at": {
+      "type": "string",
+      "format": "date-time"
+    },
+    "created_by": {
+      "type": "string"
+    },
+    "bugs": {
+      "type": "array",
+      "minItems": 1,
+      "items": {
+        "type": "object",
+        "required": [
+          "id", "title", "description", "severity",
+          "error_source", "verification_type",
+          "acceptance_criteria", "status"
+        ],
+        "properties": {
+          "id": {
+            "type": "string",
+            "pattern": "^B-\\d{3}$",
+            "description": "Bug ID, format B-001, B-002..."
+          },
+          "title": {
+            "type": "string",
+            "minLength": 1,
+            "description": "Bug title — brief description of the symptom"
+          },
+          "description": {
+            "type": "string",
+            "minLength": 1,
+            "description": "Detailed bug description: expected vs actual behavior"
+          },
+          "severity": {
+            "type": "string",
+            "enum": ["critical", "high", "medium", "low"],
+            "description": "critical=crash/data-loss; high=core-feature-broken; medium=workaround-exists; low=cosmetic"
+          },
+          "priority": {
+            "type": "integer",
+            "minimum": 1,
+            "description": "Fix priority (lower = higher priority), determines pipeline processing order"
+          },
+          "error_source": {
+            "type": "object",
+            "required": ["type"],
+            "description": "Structured error source information extracted from various input formats",
+            "properties": {
+              "type": {
+                "type": "string",
+                "enum": [
+                  "stack_trace",
+                  "user_report",
+                  "failed_test",
+                  "log_pattern",
+                  "monitoring_alert"
+                ]
+              },
+              "stack_trace": {
+                "type": "string",
+                "description": "Error stack trace (when type=stack_trace)"
+              },
+              "error_message": {
+                "type": "string",
+                "description": "Error message text"
+              },
+              "log_snippet": {
+                "type": "string",
+                "description": "Relevant log snippet (when type=log_pattern)"
+              },
+              "failed_test_path": {
+                "type": "string",
+                "description": "Path to failing test file (when type=failed_test)"
+              },
+              "reproduction_steps": {
+                "type": "array",
+                "items": { "type": "string" },
+                "description": "User-reported reproduction steps (when type=user_report)"
+              }
+            }
+          },
+          "affected_feature": {
+            "type": "string",
+            "pattern": "^F-\\d{3}(-[A-Z])?$",
+            "description": "Related original Feature ID (if any), for TRAPS cross-reference"
+          },
+          "affected_modules": {
+            "type": "array",
+            "items": { "type": "string" },
+            "description": "Known affected module names (optional, triage will auto-detect)"
+          },
+          "environment": {
+            "type": "object",
+            "description": "Environment where the bug occurs",
+            "properties": {
+              "os": { "type": "string" },
+              "runtime": { "type": "string" },
+              "browser": { "type": "string" },
+              "version": { "type": "string" }
+            }
+          },
+          "verification_type": {
+            "type": "string",
+            "enum": ["automated", "manual", "hybrid"],
+            "description": "automated=unit/integration-test; manual=human-UAT; hybrid=both"
+          },
+          "acceptance_criteria": {
+            "type": "array",
+            "minItems": 1,
+            "items": { "type": "string" },
+            "description": "Conditions that must be met for the bug to be considered fixed"
+          },
+          "status": {
+            "type": "string",
+            "enum": [
+              "pending",
+              "triaging",
+              "reproducing",
+              "fixing",
+              "verifying",
+              "completed",
+              "failed",
+              "needs_info",
+              "skipped"
+            ],
+            "description": "Bug fix status, maps to pipeline phases"
+          }
+        }
+      }
+    },
+    "global_context": {
+      "type": "object",
+      "description": "Global context for all bug fixes in this batch",
+      "properties": {
+        "tech_stack": { "type": "string" },
+        "testing_framework": { "type": "string" },
+        "ci_pipeline": { "type": "string" }
+      }
+    }
+  }
+}