Michael Tamse
25d02b8484
chore: Story 1.1 auf done setzen (Human-Review bestätigt) Co-Authored-By: Claude <noreply@anthropic.com> @
76 lines
3.2 KiB
YAML
76 lines
3.2 KiB
YAML
# STATUS DEFINITIONS:
|
|
# ==================
|
|
# Epic Status:
|
|
# - backlog: Epic not yet started
|
|
# - in-progress: Epic actively being worked on
|
|
# - done: All stories in epic completed
|
|
|
|
# Story Status:
|
|
# - backlog: Story only exists in epic file
|
|
# - ready-for-dev: Story file created, ready for development
|
|
# - in-progress: Developer actively working on implementation
|
|
# - review: Implementation complete, ready for review
|
|
# - done: Story completed
|
|
|
|
# Retrospective Status:
|
|
# - optional: Can be completed but not required
|
|
# - done: Retrospective has been completed
|
|
|
|
# Action Item Status:
|
|
# - open: Committed during a retrospective, not yet addressed
|
|
# - in-progress: Actively being worked on
|
|
# - done: Completed
|
|
|
|
# WORKFLOW NOTES:
|
|
# ===============
|
|
# - Epic transitions to 'in-progress' automatically when its first story starts (via build's sprint sync)
|
|
# - Stories can be worked in parallel if team capacity allows
|
|
# - Developer typically creates the next story after the previous one is 'done' to incorporate learnings
|
|
# - Dev moves story to 'review', then runs code-review (fresh context, different LLM recommended)
|
|
# - Retrospective appends its action items to action_items; the status view surfaces open ones
|
|
generated: 08-14-2026 00:00
|
|
last_updated: 08-14-2026 19:55
|
|
project: wow20
|
|
project_key: NOKEY
|
|
tracking_system: file-system
|
|
story_location: D:/mita/wow-2nd/_bmad-output/implementation-artifacts
|
|
development_status:
|
|
epic-1: in-progress
|
|
1-1-kanonischen-workspace-stamm-erstellen: done
|
|
1-2-sources-lokal-unter-raw-bereitstellen: backlog
|
|
1-3-okf-schema-vertrag-schema-wiki-compiler-md-autorisieren: backlog
|
|
1-4-schema-validierung-für-bundle-implementieren: backlog
|
|
epic-1-retrospective: optional
|
|
|
|
epic-2: backlog
|
|
2-1-concepts-aus-source-material-erzeugen-okf-konform: backlog
|
|
2-2-claim-granulare-provenienz-dokumentieren: backlog
|
|
2-3-concepts-verlinken-eine-erlaubte-linkform: backlog
|
|
2-4-deterministische-bereichszuordnung-concept-hierarchie: backlog
|
|
2-5-progressive-discovery-über-index-md-bereitstellen: backlog
|
|
epic-2-retrospective: optional
|
|
|
|
epic-3: backlog
|
|
3-1-inkrementellen-datenfluss-implementieren-interpret-reconcile: backlog
|
|
3-2-relevanzbestimmung-textual-deterministisch-umsetzen-grep-rip: backlog
|
|
3-3-bestehende-concepts-erweitern-präzisieren-korrigieren: backlog
|
|
3-4-wissen-aus-mehreren-sources-synthetisieren: backlog
|
|
3-5-leasing-dirty-tree-schutz-für-konkurrierende-producer-umsetz: backlog
|
|
3-6-lease-staleness-recovery-basis-absichern: backlog
|
|
3-7-reason-mutate-trennung-und-konsistenz-endzustand-sicherstell: backlog
|
|
3-8-determinismus-vertrag-ad-17h-als-agent-instruktions-validato: backlog
|
|
epic-3-retrospective: optional
|
|
|
|
epic-4: backlog
|
|
4-1-information-vor-jeder-änderung-klassifizieren-new-confirming: backlog
|
|
4-2-disagreements-in-log-md-explizit-dokumentieren: backlog
|
|
4-3-menschliche-kuratierung-respektieren-human-curation: backlog
|
|
4-4-trust-metadaten-maschinell-vs-human-reviewed-unterscheiden: backlog
|
|
epic-4-retrospective: optional
|
|
|
|
epic-5: backlog
|
|
5-1-git-nachvollziehbare-änderungen-konsistenz-commit-boundary: backlog
|
|
5-2-tool-unabhängigen-zugriff-und-agent-lesbarkeit-gewährleisten: backlog
|
|
5-3-agent-unabhängige-compiler-regeln-dünne-adapter: backlog
|
|
epic-5-retrospective: optional
|