@benzotti/jedi 0.1.0

package/framework/teams/product-research.md

@@ -0,0 +1,29 @@
+---
+name: product-research
+description: Gathers project requirements, performs research and development without writing code
+members: [jdi-ux-designer, jdi-planner, jdi-product-lead, jdi-researcher]
+---
+
+# Product and Research Team
+
+## Purpose
+
+Requirements gathering, research, and planning. Analyses designs, researches codebase patterns, defines acceptance criteria, produces implementation plans. Does NOT write code.
+
+## Members
+
+| Role | Agent | Spec Path |
+|------|-------|-----------|
+| Lead UI/UX Designer | `jdi-ux-designer` | `.jdi/framework/agents/jdi-ux-designer.md` |
+| Product Manager | `jdi-planner` | `.jdi/framework/agents/jdi-planner.md` |
+| Product Lead | `jdi-product-lead` | `.jdi/framework/agents/jdi-product-lead.md` |
+| Senior Analyst | `jdi-researcher` | `.jdi/framework/agents/jdi-researcher.md` |
+
+## Coordination
+
+Product Lead clarifies requirements → researcher investigates codebase → UX Designer maps component specs → planner synthesises into plans → Product Lead validates.
+
+## Boundaries
+
+**Will:** Analyse Figma designs, research codebase, define acceptance criteria, create plans, identify risks.
+**Won't:** Write production/test code, make commits, make architectural decisions, deploy.

package/framework/teams/quality-assurance.md

@@ -0,0 +1,27 @@
+---
+name: quality-assurance
+description: Creates and updates backend and frontend tests for completed engineering work
+members: [jdi-quality, jdi-verifier]
+---
+
+# Quality Assurance Team
+
+## Purpose
+
+Testing and verification for completed engineering work — Pest (backend) and Vitest (frontend). Ensures coverage, enforces quality gates, validates implementations against specs.
+
+## Members
+
+| Role | Agent | Spec Path |
+|------|-------|-----------|
+| Lead QA Developer | `jdi-quality` | `.jdi/framework/agents/jdi-quality.md` |
+| Senior QA Developer | `jdi-verifier` | `.jdi/framework/agents/jdi-verifier.md` |
+
+## Coordination
+
+Lead QA designs test strategy and writes tests → Senior QA performs three-level verification (Existence, Substantive, Wired) and validates against specs.
+
+## Boundaries
+
+**Will:** Design test strategies, write Pest/Vitest tests, identify edge cases, analyse coverage, verify implementations, enforce quality standards.
+**Won't:** Write production code, skip quality checks, modify source files beyond tests, make architectural decisions.

package/framework/templates/PLAN-TASK.md

@@ -0,0 +1,28 @@
+---
+plan_id: {phase}-{plan}
+task_id: {phase}-{plan}-T{n}
+task_name: {Task Name}
+type: auto
+wave: 1
+depends_on: []
+---
+
+# Task {n}: {Task Name}
+
+**Objective:** {What this task accomplishes}
+
+**Files:**
+- `{path/to/file.ts}` - {what changes}
+- `{path/to/file2.ts}` - {what changes}
+
+**Implementation:**
+1. {Step 1}
+2. {Step 2}
+3. {Step 3}
+
+**Verification:**
+- [ ] {Check 1}
+- [ ] {Check 2}
+
+**Done when:**
+- {Specific, observable completion criterion}

package/framework/templates/PLAN.md

@@ -0,0 +1,127 @@
+<section name="Frontmatter">
+
+---
+phase: {X}
+plan: {YY}
+name: {Plan Name}
+slug: {plan-slug}
+type: implementation
+autonomous: true
+wave: 1
+gap_closure: false
+
+# Split plan task files (omit for legacy monolithic plans)
+task_files:
+  - .jdi/plans/{X}-{YY}-{plan-slug}.T1.md
+  - .jdi/plans/{X}-{YY}-{plan-slug}.T2.md
+
+# Dependency Graph (enables context assembly and parallel execution)
+requires:
+  - phase: {N}
+    provides: [dependency1, dependency2]
+provides: [deliverable1, deliverable2]
+affects: [{future-phase-1}, {future-phase-2}]
+
+# Semantic Indexing (enables fast scanning and context selection)
+subsystem: {auth|api|ui|data|infra|docs|test}
+tags: [tag1, tag2, tag3]
+
+# Tech Tracking
+tech_stack:
+  added: []
+  patterns: []
+---
+
+# Phase {X} Plan {YY}: {Plan Name}
+
+---
+
+## Objective
+
+{One paragraph describing what this plan accomplishes. Be specific about the outcome.}
+
+---
+
+## Context
+
+**Read before executing:**
+- @{path/to/relevant/file}
+- @{path/to/another/file}
+
+**Relevant patterns:**
+- {Pattern to follow}
+
+**Previous work:**
+- {What's already done that this builds on}
+
+</section>
+
+---
+
+<section name="TaskManifest">
+
+## Tasks
+
+| Task | Name | Type | Wave | File |
+|------|------|------|------|------|
+| T1 | {Task Name} | auto | 1 | `{X}-{YY}-{plan-slug}.T1.md` |
+| T2 | {Task Name} | auto | 1 | `{X}-{YY}-{plan-slug}.T2.md` |
+| T3 | {Task Name} | checkpoint:human-verify | 2 | `{X}-{YY}-{plan-slug}.T3.md` |
+
+> Task details are in individual files. See `task_files` in frontmatter.
+
+</section>
+
+---
+
+<section name="Verification">
+
+## Verification
+
+After all tasks complete, verify:
+
+- [ ] {Overall verification 1}
+- [ ] {Overall verification 2}
+- [ ] Tests pass: `{test command}`
+- [ ] Types check: `{type check command}`
+
+## Success Criteria
+
+This plan is complete when:
+
+1. {Observable outcome 1}
+2. {Observable outcome 2}
+3. All tasks have commits
+4. Verification checks pass
+
+## Output
+
+**Creates:**
+- `{path/to/new/file}` - {purpose}
+
+**Modifies:**
+- `{path/to/existing/file}` - {what changes}
+
+**SUMMARY location:** `.jdi/plans/{phase}-{plan}-{slug}.summary.md`
+
+## Notes
+
+{Any additional context, warnings, or guidance for execution}
+
+</section>
+
+---
+
+<section name="DeviationRules">
+
+## Deviation Rules Reference
+
+During execution, apply automatically:
+- **Rule 1**: Auto-fix bugs
+- **Rule 2**: Auto-add critical functionality
+- **Rule 3**: Auto-fix blocking issues
+- **Rule 4**: Ask about architectural changes
+
+Document all deviations in SUMMARY.md.
+
+</section>

package/framework/templates/PROJECT.md

@@ -0,0 +1,104 @@
+# {Project Name}
+
+> {One-liner: What this is in plain language}
+
+---
+
+## What This Is
+
+{2-3 sentences describing the project. What does it do? What problem does it solve? Who is it for?}
+
+---
+
+## Core Value
+
+**The ONE thing that must work:**
+
+{Single sentence describing the critical functionality. Everything else is secondary.}
+
+---
+
+## Context
+
+### Background
+
+{Why does this project exist? What led to it?}
+
+### Users
+
+{Who will use this? What are their needs?}
+
+### Constraints
+
+| Constraint | Description |
+|------------|-------------|
+| {constraint 1} | {details} |
+| {constraint 2} | {details} |
+
+### Tech Stack
+
+{If known or decided}
+
+| Layer | Technology |
+|-------|------------|
+| Frontend | {tech} |
+| Backend | {tech} |
+| Database | {tech} |
+| Infrastructure | {tech} |
+
+---
+
+## Requirements
+
+### Validated
+
+{Requirements proven through shipped functionality}
+
+- ✓ {Requirement} — validated {date}
+
+### Active
+
+{Current scope - what's being built now}
+
+- [ ] {Requirement 1}
+- [ ] {Requirement 2}
+- [ ] {Requirement 3}
+
+### Out of Scope
+
+{Explicitly excluded - not in this version}
+
+- {Exclusion 1} — {reason}
+- {Exclusion 2} — {reason}
+
+---
+
+## Key Decisions
+
+| Decision | Rationale | Outcome |
+|----------|-----------|---------|
+| {decision 1} | {why} | {result or "Pending"} |
+
+---
+
+## Success Criteria
+
+How do we know when this is done?
+
+1. {Measurable criterion 1}
+2. {Measurable criterion 2}
+3. {Measurable criterion 3}
+
+---
+
+## References
+
+| Resource | Link |
+|----------|------|
+| Design | {Figma/design link} |
+| Ticket | {ClickUp/Jira link} |
+| Documentation | {docs link} |
+
+---
+
+*Last updated: {date} after {event}*

package/framework/templates/PROJECT.yaml

@@ -0,0 +1,16 @@
+name: "{project_name}"
+summary: "{one_liner_description}"
+
+core_value: "{the_one_thing_that_must_work}"
+
+background: "{why_this_project_exists}"
+
+constraints:
+  - "{constraint_1}"
+  - "{constraint_2}"
+
+success_criteria:
+  - "{measurable_criterion_1}"
+  - "{measurable_criterion_2}"
+
+last_updated: "{date}"

package/framework/templates/REQUIREMENTS.md

@@ -0,0 +1,95 @@
+# Requirements
+
+> Scoped requirements for {Project Name}
+
+---
+
+## Overview
+
+| Category | v1 | v2 | Out of Scope |
+|----------|----|----|--------------|
+| {Category 1} | {count} | {count} | {count} |
+| {Category 2} | {count} | {count} | {count} |
+| **Total** | **{total}** | **{total}** | **{total}** |
+
+---
+
+## v1 Requirements
+
+### {Category 1}
+
+| REQ-ID | Requirement | Priority | Status |
+|--------|-------------|----------|--------|
+| {CAT}-01 | {User can...} | High | Pending |
+| {CAT}-02 | {User can...} | Medium | Pending |
+
+#### {CAT}-01: {Short name}
+
+**Requirement:** {Full description}
+
+**Acceptance Criteria:**
+- [ ] {Criterion 1}
+- [ ] {Criterion 2}
+- [ ] {Criterion 3}
+
+**Notes:** {Any additional context}
+
+---
+
+#### {CAT}-02: {Short name}
+
+**Requirement:** {Full description}
+
+**Acceptance Criteria:**
+- [ ] {Criterion 1}
+- [ ] {Criterion 2}
+
+---
+
+### {Category 2}
+
+| REQ-ID | Requirement | Priority | Status |
+|--------|-------------|----------|--------|
+| {CAT2}-01 | {User can...} | High | Pending |
+
+---
+
+## v2 Requirements
+
+{Deferred to future version}
+
+| REQ-ID | Requirement | Reason for Deferral |
+|--------|-------------|---------------------|
+| {CAT}-03 | {User can...} | {Not critical for MVP} |
+
+---
+
+## Out of Scope
+
+{Explicitly excluded from all versions}
+
+| Item | Reason |
+|------|--------|
+| {Feature} | {Why it's excluded} |
+
+---
+
+## Traceability
+
+| REQ-ID | Phase | Plan | Status |
+|--------|-------|------|--------|
+| {CAT}-01 | 1 | 01 | Pending |
+| {CAT}-02 | 1 | 02 | Pending |
+| {CAT2}-01 | 2 | 01 | Pending |
+
+---
+
+## Change Log
+
+| Date | Change | Reason |
+|------|--------|--------|
+| {date} | Initial requirements | Project initialisation |
+
+---
+
+*Last updated: {date}*

package/framework/templates/REQUIREMENTS.yaml

@@ -0,0 +1,27 @@
+# Only active requirements. Completed phases are pruned automatically.
+
+active_phase: 1
+
+phases:
+  1:
+    name: "{phase_name}"
+    requirements:
+      "{REQ-ID}":
+        description: "{requirement_description}"
+        priority: must | should | could
+        status: pending
+        acceptance_criteria:
+          - "{criterion_1}"
+          - "{criterion_2}"
+
+out_of_scope:
+  - "{exclusion_1}: {reason}"
+
+risks:
+  - id: R-01
+    description: "{risk_description}"
+    mitigation: "{mitigation_approach}"
+
+completed_phases: []
+
+last_updated: "{date}"

package/framework/templates/ROADMAP.md

@@ -0,0 +1,116 @@
+# Roadmap
+
+> Phase structure for {Project Name}
+
+---
+
+## Overview
+
+| Phase | Name | Plans | Requirements | Status |
+|-------|------|-------|--------------|--------|
+| 1 | {name} | {count} | {REQ-IDs} | Pending |
+| 2 | {name} | {count} | {REQ-IDs} | Pending |
+| 3 | {name} | {count} | {REQ-IDs} | Pending |
+
+**Total:** {N} phases | {M} plans | {R} requirements
+
+---
+
+## Phase 1: {Phase Name}
+
+**Goal:** {What this phase achieves - one sentence}
+
+**Requirements:** {REQ-IDs covered}
+
+**Must-Haves:**
+- {Observable outcome 1}
+- {Observable outcome 2}
+- {Observable outcome 3}
+
+**Plans:**
+| Plan | Name | Tasks | Wave | Status |
+|------|------|-------|------|--------|
+| 01 | {name} | {count} | 1 | Pending |
+| 02 | {name} | {count} | 1 | Pending |
+| 03 | {name} | {count} | 2 | Pending |
+
+**Dependencies:** None (first phase)
+
+---
+
+## Phase 2: {Phase Name}
+
+**Goal:** {What this phase achieves}
+
+**Requirements:** {REQ-IDs covered}
+
+**Must-Haves:**
+- {Observable outcome 1}
+- {Observable outcome 2}
+
+**Plans:**
+| Plan | Name | Tasks | Wave | Status |
+|------|------|-------|------|--------|
+| 01 | {name} | {count} | 1 | Pending |
+| 02 | {name} | {count} | 2 | Pending |
+
+**Dependencies:** Phase 1 complete
+
+---
+
+## Phase 3: {Phase Name}
+
+**Goal:** {What this phase achieves}
+
+**Requirements:** {REQ-IDs covered}
+
+**Must-Haves:**
+- {Observable outcome 1}
+- {Observable outcome 2}
+
+**Plans:**
+| Plan | Name | Tasks | Wave | Status |
+|------|------|-------|------|--------|
+| 01 | {name} | {count} | 1 | Pending |
+
+**Dependencies:** Phase 2 complete
+
+---
+
+## Milestone Summary
+
+```
+Phase 1: {name}
+├── Plan 01: {name}
+├── Plan 02: {name}
+└── Plan 03: {name}
+
+Phase 2: {name}
+├── Plan 01: {name}
+└── Plan 02: {name}
+
+Phase 3: {name}
+└── Plan 01: {name}
+```
+
+---
+
+## Requirement Coverage
+
+| REQ-ID | Requirement | Phase | Plan |
+|--------|-------------|-------|------|
+| {CAT}-01 | {short name} | 1 | 01 |
+| {CAT}-02 | {short name} | 1 | 02 |
+| {CAT2}-01 | {short name} | 2 | 01 |
+
+**Coverage:** 100% of v1 requirements mapped
+
+---
+
+## Notes
+
+{Any additional context about the roadmap structure, sequencing decisions, etc.}
+
+---
+
+*Last updated: {date}*

package/framework/templates/ROADMAP.yaml

@@ -0,0 +1,24 @@
+# Only active phases. Completed phases are pruned automatically.
+
+overview:
+  total_phases: 1
+  completed: []
+  active: [1]
+
+phases:
+  1:
+    name: "{phase_name}"
+    status: pending
+    goal: "{what_this_phase_achieves}"
+    requirements: ["{REQ-ID-1}", "{REQ-ID-2}"]
+    must_haves:
+      - "{observable_outcome_1}"
+      - "{observable_outcome_2}"
+    plans:
+      "01":
+        name: "{plan_name}"
+        tasks: 0
+        waves: [1]
+        status: pending
+
+last_updated: "{date}"