david.delagneau
dbc1894e27
- Introduced new maps for navigating project knowledge, including "Current Work," "Fidelity Domain," "Fidelity Apps," "Work Items," and "People." - Created base files for daily notes, decisions, people, systems, work items, and workstreams with defined properties and views. - Developed templates for daily notes, decisions, meeting notes, persons, systems, work items, and workstreams to standardize documentation. - Updated scripts and prompts to reflect the new project-knowledge directory structure. - Removed outdated onboarding and start-here documents, consolidating relevant information into the new maps. - Ensured all references in workflows and scripts point to the new project-knowledge paths.
26 lines
789 B
Markdown
26 lines
789 B
Markdown
# Work Items
|
|
|
|
## Goal
|
|
|
|
Keep active Jira-linked work in one canonical place so standups, manager updates, and memory syncs can reference each ticket precisely.
|
|
|
|
---
|
|
|
|
## Structure
|
|
|
|
- `index.md`
|
|
Active index and quick status view.
|
|
|
|
- `<jira-id>.md`
|
|
Canonical file for a specific ticket.
|
|
|
|
---
|
|
|
|
## Update Rules
|
|
|
|
- Use one file per active or recently relevant Jira item.
|
|
- Keep titles exact when approved or explicitly confirmed.
|
|
- If the title is not confirmed, store the Jira ID and current framing without inventing a final title.
|
|
- Update the ticket file when scope, sequencing, points, status, rollout implications, or reproducibility meaningfully change.
|
|
- Keep `project-knowledge/01-current/work-items.md` as a short bridge summary, not the primary source of detailed ticket context.
|