TenantAtlas/specs/305-feature-readiness-gate-audit/tasks.md
Ahmed Darrazi 7796bd2304
Some checks failed
PR Fast Feedback / fast-feedback (pull_request) Failing after 7m32s
docs: add Spec 305 readiness gate audit
2026-05-15 10:57:03 +02:00

61 lines
3.1 KiB
Markdown

# Tasks: Feature Readiness Gate Audit
**Input**: Spec and plan from `/specs/305-feature-readiness-gate-audit/`
**Prerequisites**: Specs 301-304 are completed context and must remain read-only
## Format: `[ID] [P?] Description`
- **[P]**: Can run in parallel with other read-only inspection tasks
- Every task is docs-only unless explicitly listed as validation
## Phase 1: Setup
- [x] T001 Confirm current git branch and clean starting state before generating 305 artifacts.
- [x] T002 Read repo instructions, Constitution, Spec Kit templates, roadmap, and spec-candidate context.
- [x] T003 Create the 305 feature branch and initial Spec Kit plan/spec scaffold using repo scripts.
## Phase 2: Evidence Review
- [x] T004 [P] Review Specs 301-304 close-out notes and validation posture.
- [x] T005 [P] Review workspace/admin runtime provider registration and panel state.
- [x] T006 [P] Review environment-bound routes, tenant-owned resource traits, global search posture, and route retirement state.
- [x] T007 [P] Review OperationRun link and execution truth support.
- [x] T008 [P] Review governance inbox, Decision Register, findings/risk acceptance, evidence/stored report, review/review pack, RBAC, and audit/event foundations.
- [x] T009 [P] Identify relevant focused test lanes for Filament/navigation, governance, findings, evidence, reviews, OperationRun links, and legacy route retirement.
## Phase 3: Artifact Creation
- [x] T010 Replace the generated `spec.md` template with a docs-only readiness gate specification.
- [x] T011 Replace the generated `plan.md` template with a docs-only implementation plan.
- [x] T012 Create `tasks.md` for the docs-only audit workflow.
- [x] T013 Create `checklists/requirements.md` for the readiness artifact quality gate.
- [x] T014 Create `feature-readiness-audit.md` with the required repo-based matrix and GO / GO WITH CONDITIONS / NO-GO recommendation.
- [x] T015 Explicitly evaluate whether Decision Register & Approval Workflow v1 may start as the next feature spec.
## Phase 4: Validation
- [x] T016 Run focused legacy route/panel retirement tests from Specs 301-304 where practical.
- [x] T017 Run focused Filament/navigation/global-search tests from Specs 301-304 where practical.
- [x] T018 Run relevant Governance/Decision/Findings tests where practical.
- [x] T019 Run relevant Evidence/StoredReport/EnvironmentReview/ReviewPack tests where practical.
- [x] T020 Run relevant OperationRun link/legacy route tests where practical.
- [x] T021 Run `git diff --check`.
- [x] T022 Update `feature-readiness-audit.md` with validation outcomes.
## Phase 5: Close-Out
- [x] T023 Confirm `git status --short` is limited to `specs/305-feature-readiness-gate-audit/`.
- [x] T024 Confirm no application code, migrations, UI surfaces, or tests changed.
- [x] T025 Finalize the readiness recommendation and summarize residual conditions.
## Non-Goals Checklist
- [x] No runtime code changes.
- [x] No migrations.
- [x] No new UI surfaces.
- [x] No feature implementation.
- [x] No test edits.
- [x] No roadmap rewrite.
- [x] No Decision Register feature specification started.
- [x] No legacy compatibility reintroduced.