KrinosAI — Sprint Plan
Template ID: TPL-04-08 | Stage: 04-Planning | Version: 0.3
Record: KAI-VORAL-SPR-001 — retrospective draft for Visionary Oral. Not approved.
Purpose: Commit to a sprint goal and backlog items within capacity, with traceability to requirements.
Required inputs: Prioritized backlog; capacity; WBS; definition of done.
Document control
| Field |
Required entry |
| Document ID |
KAI-VORAL-SPR-001 |
| Template used |
TPL-04-08 Sprint Plan v0.3 |
| Product / project / software version or commit SHA |
VORAL (Visionary Oral) / PRJ-001 / a6b4429e3165 (branch app_dev of AI-Dental-Project/Visionary_Oral) |
| Record status and version |
Draft v0.1 |
| Author / technical reviewer / quality reviewer |
Claude Code (drafted with Claude Code for KrinosAI) / Tech Lead (name to be assigned) / Security & Privacy Officer (name to be assigned) |
| Created / updated / approved dates |
2026-10-27 / 2026-10-27 / Pending |
| Applicable SOP and revision |
SOP-LC-04 v0.3 |
| Related issue, commit, requirement and evidence links |
KAI-VORAL-PLN-001 |
| Approver and decision record |
Pending |
Applicability and evidence baseline
Product / system boundary: Web app and API (dentalapp/), doctor/admin mobile app (mobile/), PDF Lambda (dentalapp/pdf-lambda/) at a6b4429e3165, and the external services they call.
Related approved requirements, risks and change records: None approved. Related drafts are listed in document control.
Retrospective record? Yes — follows the Retrospective Documentation Protocol (KrinosAI lifecycle pack, 05-References/). Items are labelled Observed (code or Git at a6b4429), Measured (dated run), Stated (named person, dated) or Not recorded. Planning records are forward-looking: they plan the corrective work found in stages 01–03. No past project plan, estimates or sprints were recorded (OPEN-042); effort, cost and dates are left to their owners (OPEN-020, OPEN-025). No sprint has been planned or recorded; Sprint 1 below is a proposal.
Acceptable evidence: an implementation reference (file:line at a commit SHA), a dated test record, a signed decision, a vendor agreement, or another independently verifiable artifact. Never invent approvals, clinical results, measurements or performance data.
1. Sprint goal and dates
| Sprint |
Dates |
Goal |
| Sprint 1 (proposed) |
Proposed (Claude Code, for confirmation): 2026-10-29 to 2026-11-11 |
Close the critical security items |
2. Capacity
| Member |
Days available |
Notes |
| Team (STK-004, STK-005) |
Proposed (Claude Code, for confirmation): named people confirmed by their managers when the plan is approved |
Not recorded |
3. Committed backlog items
| Item |
Estimate |
REQ |
Owner |
| WP-01 (work) |
3 pd (likely; Claude Code estimate) |
REQ-035 |
Security & Privacy Officer |
| WP-02 (work) |
5 pd (likely; Claude Code estimate) |
REQ-034 |
Backend Lead |
| WP-03 (work) |
5 pd (likely; Claude Code estimate) |
REQ-034 |
Tech Lead |
4. Risks, dependencies and carry-over
| Item |
Type |
Action |
| Production deploy needed for fixes |
Dependency |
Record deployed version (OPEN-022) |
5. Sprint outcome
| Item |
Status |
Evidence |
| Sprint 1 |
Not started |
None yet |
Open issues and decisions
| ID |
Specific gap or decision |
Responsible owner |
Due date |
Blocks gate? |
Evidence required |
Status |
| OPEN-001 |
Tracker project ID, named requester and sponsor, and named reviewers are not recorded |
Product Owner |
2026-11-10 (proposed) |
Yes |
Tracker entry; names with roles |
Open |
| OPEN-020 |
No budget ceiling, contingency or cost estimates |
Sponsor |
2026-11-30 (proposed) |
Yes |
Explicit numbers |
Open |
| OPEN-022 |
Production hosting (Vercel vs Render), deployed version and dated integration checks for Clerk, MongoDB, R2, AWS, OpenRouter, Groq, Cashfree and Resend not recorded |
Tech Lead |
2026-11-30 (proposed) |
No |
Environment record (stage 05) with dated checks |
Open |
| OPEN-025 |
Milestone dates proposed only; no resources confirmed by their managers |
Sponsor |
2026-11-10 (proposed) |
Yes |
Committed dates and people |
Open |
| OPEN-042 |
No project tracker, sprint history, PR descriptions or code-review records exist for past work |
Tech Lead |
2026-12-15 (proposed) |
No |
Tracker and PR workflow in use from now on |
Open |
Review and approval
| Review role |
Named individual |
Decision |
Date |
Signed / controlled record |
| Author |
Claude Code (drafted with Claude Code) |
Draft |
2026-10-27 |
This file at the commit that adds it |
| Technical reviewer |
Tech Lead (name to be assigned) |
Pending |
Pending |
Pending |
| Quality / regulatory reviewer (if applicable) |
Qualified regulatory reviewer (name to be assigned) |
Pending |
Pending |
Pending |
| Authorized approver |
Tech Lead (name to be assigned) |
Pending |
Pending |
Pending |