prizmkit 1.0.0 → 1.0.1

package/bundled/dev-pipeline/assets/feature-list-example.json

@@ -0,0 +1,147 @@
+{
+  "$schema": "dev-pipeline-feature-list-v1",
+  "app_name": "TaskFlow",
+  "app_description": "A modern task management application with team collaboration, real-time updates, and analytics dashboard",
+  "created_at": "2026-03-04T10:00:00Z",
+  "created_by": "app-planner",
+  "source_spec": ".prizmkit/specs/app-spec.md",
+  "features": [
+    {
+      "id": "F-001",
+      "title": "Project Infrastructure Setup",
+      "description": "Initialize the monorepo structure with Next.js frontend, Express backend, and PostgreSQL database. Set up ESLint, Prettier, TypeScript configs, and CI/CD basics.",
+      "priority": 1,
+      "estimated_complexity": "medium",
+      "dependencies": [],
+      "acceptance_criteria": [
+        "Next.js app runs on port 3000",
+        "Express API runs on port 4000",
+        "PostgreSQL connection verified",
+        "TypeScript compiles without errors",
+        "ESLint and Prettier configs applied"
+      ],
+      "status": "pending",
+      "session_granularity": "feature",
+      "sub_features": []
+    },
+    {
+      "id": "F-002",
+      "title": "User Authentication",
+      "description": "Implement email/password registration and login with JWT tokens. Include password reset via email, session management, and protected routes.",
+      "priority": 2,
+      "estimated_complexity": "medium",
+      "dependencies": [
+        "F-001"
+      ],
+      "acceptance_criteria": [
+        "Users can register with email and password",
+        "Users can login and receive JWT token",
+        "Password reset flow works via email",
+        "Protected API routes reject unauthenticated requests",
+        "Session persists across page refreshes"
+      ],
+      "status": "pending",
+      "session_granularity": "feature",
+      "sub_features": []
+    },
+    {
+      "id": "F-003",
+      "title": "Task CRUD Operations",
+      "description": "Core task management: create, read, update, delete tasks. Tasks have title, description, status (todo/in-progress/done), priority, due date, and assignee.",
+      "priority": 3,
+      "estimated_complexity": "medium",
+      "dependencies": [
+        "F-002"
+      ],
+      "acceptance_criteria": [
+        "Create task with all required fields",
+        "List tasks with pagination and filtering",
+        "Update task status, title, description",
+        "Delete task with confirmation",
+        "Task validation enforced on both client and server"
+      ],
+      "status": "pending",
+      "session_granularity": "feature",
+      "sub_features": []
+    },
+    {
+      "id": "F-004",
+      "title": "Project & Team Management",
+      "description": "Organize tasks into projects. Support team creation, member invitation, and role-based permissions (owner, admin, member, viewer).",
+      "priority": 4,
+      "estimated_complexity": "high",
+      "dependencies": [
+        "F-003"
+      ],
+      "acceptance_criteria": [
+        "Create and manage projects",
+        "Invite team members via email",
+        "Role-based access control enforced",
+        "Project-level task filtering",
+        "Team member list with role display"
+      ],
+      "status": "pending",
+      "session_granularity": "auto",
+      "sub_features": [
+        {
+          "id": "F-004-A",
+          "title": "Project CRUD & Organization",
+          "description": "Create, read, update, delete projects. Associate tasks with projects."
+        },
+        {
+          "id": "F-004-B",
+          "title": "Team & Permissions",
+          "description": "Team creation, member invitation, role-based access control."
+        }
+      ]
+    },
+    {
+      "id": "F-005",
+      "title": "Real-time Updates",
+      "description": "Add WebSocket-based real-time notifications for task changes, comments, and team activity. Show live updates without page refresh.",
+      "priority": 5,
+      "estimated_complexity": "high",
+      "dependencies": [
+        "F-003"
+      ],
+      "acceptance_criteria": [
+        "Task status changes appear in real-time for team members",
+        "New comments trigger live notifications",
+        "Connection status indicator shown in UI",
+        "Graceful fallback when WebSocket disconnects",
+        "No duplicate notifications"
+      ],
+      "status": "pending",
+      "session_granularity": "feature",
+      "sub_features": []
+    },
+    {
+      "id": "F-006",
+      "title": "Analytics Dashboard",
+      "description": "Dashboard showing task completion rates, team productivity metrics, overdue task tracking, and project progress visualization.",
+      "priority": 6,
+      "estimated_complexity": "medium",
+      "dependencies": [
+        "F-004",
+        "F-005"
+      ],
+      "acceptance_criteria": [
+        "Task completion rate chart (daily/weekly/monthly)",
+        "Team productivity leaderboard",
+        "Overdue task alerts and summary",
+        "Project progress bars",
+        "Date range filtering for all charts"
+      ],
+      "status": "pending",
+      "session_granularity": "feature",
+      "sub_features": []
+    }
+  ],
+  "global_context": {
+    "tech_stack": "Next.js 14 + Express.js + PostgreSQL + Prisma ORM",
+    "design_system": "shadcn/ui + Tailwind CSS",
+    "testing_strategy": "Jest (unit) + Playwright (e2e)",
+    "deployment": "Docker + Vercel (frontend) + Railway (backend)",
+    "language": "TypeScript"
+  }
+}

package/bundled/dev-pipeline/assets/prizm-dev-team-integration.md

@@ -0,0 +1,138 @@
+# prizm-dev-team Integration Guide
+
+## Overview
+
+dev-pipeline drives the prizm-dev-team multi-agent team through an outer shell loop. Each iteration spawns a new CodeBuddy CLI session with a bootstrap prompt that instructs the agent to create and orchestrate the team for one feature.
+
+## Architecture
+
+```
+dev-pipeline (outer loop)
+    │
+    ├── run.sh                    Shell runner — picks next feature, spawns CLI
+    ├── scripts/                  Python state management scripts
+    ├── templates/bootstrap-prompt.md  Session prompt template
+    │
+    └── [per session] CodeBuddy CLI
+            │
+            ├── TeamCreate("prizm-dev-team-F-NNN")
+            ├── Spawn Coordinator agent
+            │       │
+            │       ├── Phase 0: Init
+            │       ├── Phase 1-4: PM (specify/plan/tasks/analyze)
+            │       ├── Phase 5: Schedule & Assign
+            │       ├── Phase 6: Dev x N (parallel implement)
+            │       ├── Phase 7: QA + Review (parallel)
+            │       ├── Phase 8: Fix Loop (max 3 rounds)
+            │       └── Phase 9: Summarize & Commit
+            │
+            └── Write session-status.json → exit
+```
+
+## Agent Definitions (Source of Truth)
+
+| Agent | Definition Path | Type |
+|-------|----------------|------|
+| Coordinator | `agent-team-master/prizm-dev-team/prizm-dev-team-coordinator/subagent.md` | prizm-dev-team-coordinator |
+| PM | `agent-team-master/prizm-dev-team/prizm-dev-team-pm/subagent.md` | prizm-dev-team-pm |
+| Dev | `agent-team-master/prizm-dev-team/prizm-dev-team-dev/subagent.md` | prizm-dev-team-dev |
+| QA | `agent-team-master/prizm-dev-team/prizm-dev-team-qa/subagent.md` | prizm-dev-team-qa |
+| Review | `agent-team-master/prizm-dev-team/prizm-dev-team-review/subagent.md` | prizm-dev-team-review |
+| Doc-Reader | `agent-team-master/prizm-dev-team/prizm-dev-team-doc-reader/subagent.md` | prizm-dev-team-doc-reader |
+
+## Validator Scripts
+
+Located at `agent-team-master/prizm-dev-team/prizm-dev-team-coordinator/scripts/`:
+
+| Script | Checkpoint | Purpose |
+|--------|-----------|---------|
+| `init-dev-team.py` | CP-0 | Initialize `.dev-team/` + `.prizmkit/` directories |
+| `validate-json-schema.py` | CP-1,2,3 | Validate JSON artifacts against schemas |
+| `validate-dag.py` | CP-3 | Verify dependency graph has no cycles |
+| `validate-report-format.py` | CP-6,7 | Check Markdown reports have required sections |
+| `check-contract-integrity.py` | CP-3,6,7 | SHA-256 hash verification for contracts |
+
+## Artifact Mapping
+
+### PrizmKit Artifacts (.prizmkit/)
+
+| Phase | File | Content |
+|-------|------|---------|
+| 1 | `specs/spec.md` | Feature specification (WHAT/WHY) |
+| 2 | `plans/plan.md` | Technical plan (architecture, API, tests) |
+| 3 | `tasks/tasks.md` | Executable task list with `[ ]` / `[x]` |
+| 4 | `analysis/analyze-report.md` | Consistency analysis |
+| 9 | `specs/REGISTRY.md` | Completed features archive |
+
+### Dev-Team Artifacts (.dev-team/)
+
+| Phase | File | Content |
+|-------|------|---------|
+| 1 | `specs/requirements.md` | Requirements with REQ-NNN IDs |
+| 2 | `contracts/*.contract.json` | Interface contracts |
+| 2 | `contracts/data-models.json` | Data entity definitions |
+| 3 | `tasks/task-manifest.json` | Structured tasks with T-NNN IDs |
+| 3 | `tasks/dependency-graph.json` | Task DAG |
+| 6 | `reports/dev/self-test-*.md` | Dev self-test reports |
+| 7 | `reports/qa/integration-test.md` | QA integration test report |
+| 7 | `reports/review/code-review.md` | Review report |
+
+## Session Lifecycle
+
+### 1. Session Start
+
+The bootstrap prompt instructs the agent to:
+- Create a team named `prizm-dev-team-{FEATURE_ID}`
+- Spawn the Coordinator with the full subagent.md prompt
+- Coordinator then spawns PM, Dev, QA, Review as needed
+
+### 2. Pipeline Execution
+
+The Coordinator drives the 10-phase pipeline with 8 checkpoints (CP-0 through CP-7). Each checkpoint validates artifacts using the validator scripts.
+
+### 3. Session End
+
+The agent MUST write `session-status.json` before exiting:
+
+```json
+{
+  "session_id": "F-001-20260304100000",
+  "feature_id": "F-001",
+  "status": "success",
+  "completed_phases": [0, 1, 2, 3, 4, 5, 6, 7, 8, 9],
+  "current_phase": 9,
+  "checkpoint_reached": "CP-7",
+  "tasks_completed": 12,
+  "tasks_total": 12,
+  "errors": [],
+  "can_resume": false,
+  "resume_from_phase": null,
+  "artifacts": {
+    "spec_path": ".prizmkit/specs/spec.md",
+    "plan_path": ".prizmkit/plans/plan.md",
+    "tasks_path": ".prizmkit/tasks/tasks.md"
+  },
+  "timestamp": "2026-03-04T11:30:00Z"
+}
+```
+
+## Failure Recovery
+
+| Session Outcome | Pipeline Action |
+|-----------------|-----------------|
+| `status: "success"` | Mark feature completed, pick next |
+| `status: "partial"`, `can_resume: true` | Resume from `resume_from_phase` |
+| `status: "partial"`, `can_resume: false` | Retry from scratch |
+| `status: "failed"` | Retry (up to MAX_RETRIES) |
+| No status file (crash) | Treat as failed, retry |
+| Timeout (exit 124) | Treat as timed_out, retry |
+
+## Team Naming Convention
+
+Each feature gets its own team instance: `prizm-dev-team-{FEATURE_ID}`
+
+Examples:
+- `prizm-dev-team-F-001` — User Authentication
+- `prizm-dev-team-F-002` — Dashboard
+
+This ensures clean isolation between features and allows multiple features to have separate artifact histories.