tasks ready

.opencode/command/speckit.plan.md

@@ -1,13 +1,13 @@
 ---
-description: Execute the Rust MCP implementation planning workflow and generate research, design, contracts, and quickstart artifacts.
+description: Execute the Python/Svelte implementation planning workflow and generate research, design, contracts, and quickstart artifacts.
 handoffs:
   - label: Create Tasks
     agent: speckit.tasks
-    prompt: Break the Rust MCP plan into executable tasks
+    prompt: Break the Python/Svelte plan into executable tasks
     send: true
   - label: Create Checklist
     agent: speckit.checklist
-    prompt: Create a requirements-quality checklist for the active Rust MCP feature
+    prompt: Create a requirements-quality checklist for the active Python/Svelte feature
 ---
 
 ## User Input
@@ -27,20 +27,19 @@ You **MUST** consider the user input before proceeding (if not empty).
 
 2. **Load canonical planning context**:
    - `README.md`
-   - `Cargo.toml`
+   - `backend/pyproject.toml` and `backend/requirements.txt`
+   - `frontend/package.json` and `frontend/svelte.config.js`
    - `docs/SEMANTIC_PROTOCOL_COMPLIANCE.md`
-   - `docs/adr/ADR-0001-semantic-rust-module-layout.md`
-   - `docs/adr/ADR-0002-belief-state-runtime.md`
-   - `docs/adr/ADR-0003-comment-anchored-semantic-protocol.md`
-   - `docs/adr/ADR-0004-task-shaped-server-routing.md`
+   - `docs/adr/*.md` (Architecture Decision Records)
    - `.specify/memory/constitution.md`
-   - `.kilo/skills/semantics-core/SKILL.md`
-   - `.kilo/skills/semantics-contracts/SKILL.md`
-   - `.kilo/skills/semantics-testing/SKILL.md`
+   - `.opencode/skills/semantics-core/SKILL.md`
+   - `.opencode/skills/semantics-contracts/SKILL.md`
+   - `.opencode/skills/semantics-testing/SKILL.md`
+   - `.opencode/skills/semantics-frontend/SKILL.md`
    - `.specify/templates/plan-template.md`
 
 3. **Execute the planning workflow** using the template structure:
-    - Fill `Technical Context` for the current repository reality: Rust crate, task-shaped MCP server, semantic contracts, belief runtime, and repository-local verification.
+    - Fill `Technical Context` for the current repository reality: Python 3.13+ backend (FastAPI, SQLAlchemy), Svelte 5 frontend (SvelteKit, Vite, Tailwind CSS), PostgreSQL storage, Docker deployment.
     - Fill `Constitution Check` using the local constitution, semantic protocol compliance doc, and ADR set.
     - ERROR if a blocking constitutional or semantic conflict is discovered and cannot be justified.
     - Phase 0: generate `research.md` in `FEATURE_DIR`, resolving all material unknowns.
@@ -52,14 +51,16 @@ You **MUST** consider the user input before proceeding (if not empty).
 
 ## Phase 0: Research
 
-Research must resolve only implementation-shaping unknowns that matter for this Rust MCP repository, such as:
+Research must resolve only implementation-shaping unknowns that matter for this Python/Svelte repository, such as:
 
-- crate/module placement under `src/`
-- `tests/*.rs` strategy and required fixture coverage
-- MCP tool/resource schema design
-- runtime evidence and belief-state coverage
+- backend module placement under `backend/src/` (api/, core/, models/, services/, schemas/)
+- frontend component placement under `frontend/src/` (routes/, lib/components/, lib/stores/, lib/api/)
+- `backend/tests/` and `frontend/tests/` strategy and required fixture coverage
+- FastAPI endpoint / WebSocket schema design
+- Svelte 5 runes reactivity model ($state, $derived, $effect, $props)
+- PostgreSQL schema and migration strategy
+- belief-state runtime coverage for C4/C5 Python flows
 - semantic validation boundaries and static verification workflow
-- task-shaped routing, workspace safety, and error-envelope design
 
 Write `research.md` with concise sections:
 
@@ -74,29 +75,34 @@ Use `[NEED_CONTEXT: target]` instead of inventing relation targets, DTO names, o
 
 ### UX / Interaction Validation
 
-Validate the proposed design against `ux_reference.md` as an **interaction reference** for MCP callers, CLI/operator flows, result envelopes, warnings, and recovery guidance.
+Validate the proposed design against `ux_reference.md` as an **interaction reference** for:
+- API callers (REST endpoints, WebSocket messages)
+- CLI/operator flows
+- Svelte UI flows (when the feature introduces frontend components)
+- Result envelopes, warnings, and recovery guidance
 
 If the planned architecture degrades the promised interaction model, deterministic recovery path, or context-budget behavior, stop and warn the user.
 
 ### Data Model Output
 
-Generate `data-model.md` for Rust/MCP domain entities such as:
+Generate `data-model.md` for Python/Svelte domain entities such as:
 
-- tool request/response structs
-- semantic query payloads
-- runtime evidence envelopes
-- workspace/checkpoint/index/security entities
-- contract and relation traceability data
+- FastAPI request/response schemas (Pydantic models)
+- SQLAlchemy ORM entities
+- Svelte store shapes and component props
+- WebSocket message envelopes
+- Task/report/artifact entities
 
 ### Global ADR Continuity
 
 Before task decomposition, planning must identify any repo-shaping decisions this feature depends on or extends:
 
-- Rust module layout and decomposition
-- task-shaped tool/resource routing
-- belief-state runtime behavior
-- semantic comment-anchor rules
-- payload/schema stability decisions
+- Python module layout and decomposition (`backend/src/api/`, `backend/src/core/`, etc.)
+- Frontend component architecture (Svelte 5 runes, SvelteKit routing)
+- Belief-state runtime behavior for C4/C5 flows
+- Semantic comment-anchor rules for Python and Svelte
+- RBAC/security constraints (local auth, ADFS SSO)
+- Plugin system lifecycle
 
 For each durable choice, ensure the plan references the relevant ADR and explicitly records accepted and rejected paths.
 
@@ -108,37 +114,35 @@ Generate `contracts/modules.md` as the primary design contract for implementatio
 - classify each planned module/component with `@COMPLEXITY` 1-5
 - use canonical relation syntax `@RELATION PREDICATE -> TARGET_ID`
 - preserve accepted-path and rejected-path memory via `@RATIONALE` and `@REJECTED` where needed
-- describe MCP tools/resources, runtime evidence, validation envelopes, and semantic boundaries instead of inventing backend/frontend layers
+- describe Python backend modules (api routes, core services, models, plugins) and Svelte frontend components instead of inventing Rust/MCP layers
+- use appropriate comment-anchor syntax: `# [DEF:...]` for Python, `<!-- [DEF:...] -->` for Svelte markup, `// [DEF:...]` for Svelte script blocks
 
 Complexity guidance for this repository:
 
-- **Complexity 1**: anchors only
-- **Complexity 2**: `@PURPOSE`
-- **Complexity 3**: `@PURPOSE`, `@RELATION`
-- **Complexity 4**: `@PURPOSE`, `@RELATION`, `@PRE`, `@POST`, `@SIDE_EFFECT`; Rust orchestration paths should account for belief runtime markers before mutation or return
+- **Complexity 1**: anchors only (DTOs, simple constants)
+- **Complexity 2**: `@PURPOSE` (utility functions, pure helpers)
+- **Complexity 3**: `@PURPOSE`, `@RELATION` (multi-step flows with dependencies); Svelte components also `@UX_STATE`
+- **Complexity 4**: `@PURPOSE`, `@RELATION`, `@PRE`, `@POST`, `@SIDE_EFFECT`; Python orchestration paths should account for belief runtime markers (`belief_scope`, `reason`, `reflect`, `explore`); Svelte also `@UX_FEEDBACK`, `@UX_RECOVERY`, `@UX_REACTIVITY`
 - **Complexity 5**: level 4 plus `@DATA_CONTRACT`, `@INVARIANT`, and explicit decision-memory continuity
 
 If a planned contract depends on unknown schema, relation target, or ADR identity, emit `[NEED_CONTEXT: target]` instead of fabricating placeholders.
 
-### Optional Machine-Readable Contracts
-
-You MAY generate machine-readable artifacts in `contracts/` only when they mirror the actual MCP tool/resource payloads of this Rust server. Do **not** default to REST/OpenAPI or frontend-sync artifacts unless the feature truly introduces them.
-
 ### Quickstart Output
 
-Generate `quickstart.md` using real repository verification paths, typically:
+Generate `quickstart.md` using real repository verification paths:
 
-- start or exercise the MCP server entrypoint
-- invoke relevant MCP tools/resources
-- validate expected envelopes and recovery flows
-- run `cargo test --all-targets --all-features -- --nocapture`
-- run `cargo clippy --all-targets --all-features -- -D warnings` when applicable
-- run `python3 scripts/static_verify.py`
+- start or exercise the FastAPI backend entrypoint: `cd backend && python -m uvicorn src.app:app --reload`
+- start or exercise the SvelteKit frontend: `cd frontend && npm run dev`
+- invoke relevant API endpoints or CLI commands
+- validate expected response envelopes, WebSocket messages, and recovery flows
+- run `cd backend && pytest` for backend tests
+- run `cd frontend && npm run test` for frontend tests
+- run `ruff check backend/` for Python linting
 
 ## Key Rules
 
 - Use absolute paths in workflow execution.
-- Planning must reflect the current repository structure (`src/**/*.rs`, `tests/*.rs`, `docs/adr/*`) rather than legacy Python/Svelte examples.
-- Do not reference `.ai/*` or `.kilocode/*` paths.
+- Planning must reflect the current repository structure (`backend/src/`, `frontend/src/`, `docs/adr/`) rather than legacy Rust/MCP examples.
+- Do not reference `.ai/*` or `.kilocode/*` paths as feature artifacts.
 - Do not write any feature planning artifact outside `specs/<feature>/...`.
 - Do not hand off to `speckit.tasks` until blocking ADR continuity and rejected-path guardrails are explicit.