contextcompass 2.15.0__py3-none-any.whl

contextcompass_cli/_package/templates/story_template.md

@@ -0,0 +1,131 @@
+
+
+# Story: <short, outcome-focused title>
+
+## Metadata
+- Story ID: STORY-YYYY-MM-DD-<slug>
+- Epic: EPIC-YYYY-MM-DD-<slug>
+- Status: draft | ready | in_progress | blocked | done
+- Owner:
+- Agent Name: <one or more assigned names, comma-separated>
+- Priority: p0 | p1 | p2 | p3
+- Created: YYYY-MM-DDTHH:MM:SSZ
+- Updated: YYYY-MM-DDTHH:MM:SSZ
+
+## User Narrative
+As a <user/persona>, I want <capability>, so that <outcome>.
+
+## Value / MRP Alignment
+<Explain how this story strengthens the holistic core.>
+
+## Ticket Contract
+- ENTRY_GATE: <active board row and linked task/story prerequisites satisfied>
+- EXECUTION_BOUNDARY: <story-level surfaces allowed; no unrelated expansion>
+- DEPENDENCIES: <task set and prerequisite tickets/stories/epic milestones>
+- EXIT_GATE: <acceptance + child-task state + board-sync requirements>
+- FAILURE_ESCALATION: <when to raise DECISION_REQUEST/CONFLICT/BLOCKER>
+
+## Requirements (Functional)
+- 
+
+## Requirements (Non-Functional)
+- 
+
+## Scope Boundaries
+- In scope:
+- Out of scope:
+
+## State Transition Event
+- from_state: draft | ready | in_progress | blocked | review
+- to_state: ready | in_progress | blocked | review | done
+- transition_reason: <why this transition is valid now>
+
+## Dependencies / Related Work
+- 
+
+## Tasks (Implementation Checklist)
+- [ ] Task: <TASK-ID> - <short description>
+- [ ] Task: <TASK-ID> - <short description>
+- [ ] Enforce Ticket Microcycle across all linked tasks.
+- [ ] Require meaningful-finding note updates during discovery/implementation.
+
+## Acceptance Criteria
+- 
+
+## Validation / Test Plan
+- 
+
+## UX / API / Data Notes
+- 
+
+## Risks / Mitigations
+- 
+
+## Applicable Anti-Patterns
+- [ ] No story-state transition without linked task-state evidence.
+- [ ] No closure while required tasks remain active or un-routed.
+- [ ] No cross-task synthesis claims without ticket-note evidence pointers.
+
+## Open Questions
+- 
+
+## Decision Log
+- 
+
+## Artifact Links (Optional)
+- ARTIFACTS_REQUIRED: true | false
+- ARTIFACT_PATHS:
+  - <artifacts/YYYY-MM-DD_<slug>.<ext>>
+- DISPOSITION: delete_on_close | retain_as_reference | promote_to_documentation
+- CLEANUP_TRIGGER: <when artifact cleanup/retention decision is applied>
+
+## Context Management
+- CONTEXT_MANAGEMENT_REQUIRED: true | false
+- CONTEXT_IDS:
+  - CTX-YYYY-MM-DD-<slug> | UNKNOWN
+- CONTEXT_TOPICS:
+  - <topic or question> | UNKNOWN
+- IF_UNKNOWN: UNKNOWN | ask user before implementation | none
+
+## Notes
+- DATETIME: YYYY-MM-DDTHH:MM:SSZ
+  TYPE:
+    FACT | UNKNOWN | HYPOTHESIS | DECISION | DECISION_REQUEST | PLAN |
+    STRATEGY_DISCUSSION | ASSUMPTION_CHALLENGE | CONFLICT | TRADEOFF |
+    BLOCKER | ALIGNMENT_CHECK | MEASURE | RISK | RAISE
+  CLAIM: <short finding>
+  EVIDENCE:
+  - <path:start_line-end_line>
+  - <path:start_line-end_line>
+  IMPACT: <why this matters>
+  NEXT: <one concrete next action>
+  REREAD: REQUIRED | HELPFUL
+  SCORE_0_TO_10: <0-10 compaction usefulness>
+
+## Closure Confirmation
+- [ ] Work walkthrough shared with user
+- [ ] Acceptance criteria confirmed by user
+- [ ] Applicable anti-pattern checks are clear or escalated with evidence.
+
+## Noting Behavior
+- Note focus: cross-task synthesis, dependency flow, and state-transition logic.
+- Add notes when task routing changes, gate decisions are made, or risks shift.
+- Reference child-task notes for evidence instead of duplicating tactical detail.
+- Keep notes append-only and preserve UNKNOWN-first promotion discipline.
+
+## Context / Handoff Summary
+<Succinct summary of current state, key decisions, and next steps for future context.>
+
+## Project-Specific Additions
+<!-- BEGIN USER-DEFINED: project_fields -->
+<!-- END USER-DEFINED: project_fields -->
+
+<!--
+Anything this project needs on every ticket of this kind goes in the region
+above: extra fields, a compliance checklist, a link to a local convention.
+
+The region is yours. An upgrade replaces every other line of this template with
+the new version's text and carries this region across untouched, so a local
+addition here is not a divergence you re-resolve on every upgrade - which is
+what editing the rest of the template would cost you.
+-->

contextcompass_cli/_package/templates/task_template.md

@@ -0,0 +1,124 @@
+
+
+# Task: <short, action-focused title>
+
+## Metadata
+- Task ID: TASK-YYYY-MM-DD-<slug>
+- Story: STORY-YYYY-MM-DD-<slug>
+- Status: draft | ready | in_progress | blocked | done
+- Owner:
+- Agent Name: <one or more assigned names, comma-separated>
+- Priority: p0 | p1 | p2 | p3
+- Created: YYYY-MM-DDTHH:MM:SSZ
+- Updated: YYYY-MM-DDTHH:MM:SSZ
+
+## Objective
+<Define the smallest meaningful outcome this task delivers.>
+
+## Ticket Contract
+- ENTRY_GATE: <active board row and latest note requirements before work starts>
+- EXECUTION_BOUNDARY: <files/symbols/surfaces allowed in this task>
+- DEPENDENCIES: <upstream/downstream tickets or docs this task depends on>
+- EXIT_GATE: <conditions required before status can move to review/done>
+- FAILURE_ESCALATION: <when to record DECISION_REQUEST/CONFLICT/BLOCKER>
+
+## Scope Boundaries
+- In scope:
+- Out of scope:
+
+## State Transition Event
+- from_state: draft | ready | in_progress | blocked | review
+- to_state: ready | in_progress | blocked | review | done
+- transition_reason: <why this transition is valid now>
+
+## Steps / Checklist
+- [ ] 
+- [ ] 
+- [ ] Run Ticket Microcycle during execution:
+      `Investigate -> Document -> Strategy/Plan -> Document -> Implement ->
+      Document -> Validate -> Document`.
+- [ ] Document each meaningful finding immediately in `## Notes` before further investigation.
+
+## Deliverables
+- 
+
+## Files / Paths Impacted
+- 
+
+## Validation
+- Not run.
+- Recommended commands:
+  - 
+
+## Risks / Rollback Notes
+- 
+
+## Applicable Anti-Patterns
+- [ ] No status transition without evidence-backed transition reason.
+- [ ] No implementation/validation from `UNKNOWN` or `HYPOTHESIS`.
+- [ ] No closure without acceptance confirmation and board-sync completion.
+
+## Done Checklist
+- [ ] Steps complete and checked off
+- [ ] Deliverables produced and linked
+- [ ] Documentation updated (if needed)
+- [ ] Validation status recorded
+- [ ] Unknown-first discipline followed (`UNKNOWN` promoted to `FACT` only with evidence)
+- [ ] Notes quality maintained (`SCORE_0_TO_10` >=
+      `workflow.ticket_microcycle.minimum_note_score`)
+- [ ] Applicable anti-pattern checks are clear or escalated with evidence.
+- [ ] Acceptance criteria reviewed with user and confirmed
+- [ ] Board sync completed for successor routing or closure anchor update.
+
+## Artifact Links (Optional)
+- ARTIFACTS_REQUIRED: true | false
+- ARTIFACT_PATHS:
+  - <artifacts/YYYY-MM-DD_<slug>.<ext>>
+- DISPOSITION: delete_on_close | retain_as_reference | promote_to_documentation
+- CLEANUP_TRIGGER: <when artifact cleanup/retention decision is applied>
+
+## Context Management
+- CONTEXT_MANAGEMENT_REQUIRED: true | false
+- CONTEXT_IDS:
+  - CTX-YYYY-MM-DD-<slug> | UNKNOWN
+- CONTEXT_TOPICS:
+  - <topic or question> | UNKNOWN
+- IF_UNKNOWN: UNKNOWN | ask user before implementation | none
+
+## Noting Behavior
+- Note focus: tactical findings, concrete impacts, and single-step continuation.
+- Add a `## Notes` entry after each meaningful finding before continuing.
+- Keep notes append-only; correct history only for factual errors.
+- Promote `UNKNOWN` to `FACT` only with direct evidence pointers.
+
+## Notes
+- DATETIME: YYYY-MM-DDTHH:MM:SSZ
+  TYPE:
+    FACT | UNKNOWN | HYPOTHESIS | DECISION | DECISION_REQUEST | PLAN |
+    STRATEGY_DISCUSSION | ASSUMPTION_CHALLENGE | CONFLICT | TRADEOFF |
+    BLOCKER | ALIGNMENT_CHECK | MEASURE | RISK | RAISE
+  CLAIM: <short finding>
+  EVIDENCE:
+  - <path:start_line-end_line>
+  - <path:start_line-end_line>
+  IMPACT: <why this matters>
+  NEXT: <one concrete next action>
+  REREAD: REQUIRED | HELPFUL
+  SCORE_0_TO_10: <0-10 compaction usefulness>
+
+## Context / Handoff Summary
+<Succinct summary of current state, key decisions, and next steps for future context.>
+
+## Project-Specific Additions
+<!-- BEGIN USER-DEFINED: project_fields -->
+<!-- END USER-DEFINED: project_fields -->
+
+<!--
+Anything this project needs on every ticket of this kind goes in the region
+above: extra fields, a compliance checklist, a link to a local convention.
+
+The region is yours. An upgrade replaces every other line of this template with
+the new version's text and carries this region across untouched, so a local
+addition here is not a divergence you re-resolve on every upgrade - which is
+what editing the rest of the template would cost you.
+-->

contextcompass_cli/_package/templates/workflow_advanced_template.md

@@ -0,0 +1,111 @@
+# Workflow: <short outcome-focused title>
+
+## Metadata
+- Workflow ID: WF-<slug>
+- Status: draft | ready | active | deprecated
+- Owner:
+- Allowed Roles:
+- Default Roles:
+- Trigger:
+- Created: YYYY-MM-DDTHH:MM:SSZ
+- Updated: YYYY-MM-DDTHH:MM:SSZ
+
+## Purpose
+<What macro behavior this workflow provides.>
+
+## Use When
+- <valid trigger 1>
+- <valid trigger 2>
+
+## Do Not Use When
+- <invalid trigger 1>
+- <invalid trigger 2>
+
+## Inputs
+- Required:
+- Optional:
+
+## Outputs
+- Expected artifacts:
+- Expected ticket state:
+- Expected board state:
+
+## Required Reads
+- <doc path>
+- <doc path>
+
+## Required Skills
+- <skill path>
+- <skill path>
+
+## Preconditions / Gates
+- <gate 1>
+- <gate 2>
+
+## Phase Sequence
+1. Intake
+- objective:
+- required actions:
+- stop conditions:
+
+2. Investigation
+- objective:
+- required actions:
+- required note or artifact updates:
+
+3. Strategy
+- objective:
+- decision points:
+
+4. Implementation
+- objective:
+- scope controls:
+
+5. Validation
+- objective:
+- required checks:
+
+6. Handoff / Closure
+- objective:
+- required board or ticket sync:
+
+## Ticket Behavior
+- Required ticket types:
+- Required metadata:
+- Required note cadence:
+- Required artifact links:
+
+## Attention Board Behavior
+- Required row fields:
+- Mode transitions:
+- Exit signal rules:
+
+## Escalation Rules
+- <when to stop>
+- <when to raise DECISION_REQUEST>
+- <when to raise BLOCKER>
+
+## Success Criteria
+- <condition 1>
+- <condition 2>
+
+## Anti-Patterns
+- <bad behavior 1>
+- <bad behavior 2>
+
+## Context / Handoff Summary
+<What a future agent must know to resume safely.>
+
+## Project-Specific Additions
+<!-- BEGIN USER-DEFINED: project_fields -->
+<!-- END USER-DEFINED: project_fields -->
+
+<!--
+Anything this project needs on every ticket of this kind goes in the region
+above: extra fields, a compliance checklist, a link to a local convention.
+
+The region is yours. An upgrade replaces every other line of this template with
+the new version's text and carries this region across untouched, so a local
+addition here is not a divergence you re-resolve on every upgrade - which is
+what editing the rest of the template would cost you.
+-->

contextcompass_cli/_package/templates/workflow_simple_template.md

@@ -0,0 +1,65 @@
+# Workflow: <short outcome-focused title>
+
+## Metadata
+- Workflow ID: WF-<slug>
+- Status: draft | ready | active | deprecated
+- Owner:
+- Created: YYYY-MM-DDTHH:MM:SSZ
+- Updated: YYYY-MM-DDTHH:MM:SSZ
+
+## Purpose
+<What macro behavior this workflow provides.>
+
+## Required Reads
+- <doc path>
+- <doc path>
+
+## Required Skills
+- <skill path>
+- <skill path>
+
+## Phase Sequence
+1. Intake
+- objective:
+- required actions:
+- stop conditions:
+
+2. Investigation
+- objective:
+- required actions:
+- required note or artifact updates:
+
+3. Strategy
+- objective:
+- decision points:
+
+4. Implementation
+- objective:
+- scope controls:
+
+5. Validation
+- objective:
+- required checks:
+
+6. Handoff / Closure
+- objective:
+- required board or ticket sync:
+
+## Attention Board Behavior
+- Required row fields:
+- Mode transitions:
+- Exit signal rules:
+
+## Project-Specific Additions
+<!-- BEGIN USER-DEFINED: project_fields -->
+<!-- END USER-DEFINED: project_fields -->
+
+<!--
+Anything this project needs on every ticket of this kind goes in the region
+above: extra fields, a compliance checklist, a link to a local convention.
+
+The region is yours. An upgrade replaces every other line of this template with
+the new version's text and carries this region across untouched, so a local
+addition here is not a divergence you re-resolve on every upgrade - which is
+what editing the rest of the template would cost you.
+-->

contextcompass_cli/_package/tickets/README.md

@@ -0,0 +1,24 @@
+
+
+# Tickets
+
+Purpose
+- User-facing index for ticket storage.
+- Keep ticket lanes grouped in one root for easier navigation.
+
+Structure
+- `tickets/epics/`: active and backlog epic tickets.
+- `tickets/stories/`: active and backlog story tickets.
+- `tickets/tasks/`: active and backlog task tickets.
+- `tickets/*/completed/`: completed tickets per lane.
+
+Backlog locations
+- `tickets/epics/backlog/`
+- `tickets/stories/backlog/`
+- `tickets/tasks/backlog/`
+
+Notes
+- Active routing still comes from `attention_board.md`.
+- Durable execution memory still lives in each active ticket `## Notes`.
+
+

contextcompass_cli/_package/tickets/epics/README.md

@@ -0,0 +1,68 @@
+
+
+# Epics
+
+## Purpose
+Epics capture multi-story outcomes that define durable, MRP-aligned changes. They are the
+top-level planning unit and must be rich enough to survive context compaction.
+
+## MRP First (Required)
+- Every epic must describe the holistic core being built and why it is the right foundation.
+- MRP means "reasonable," not "minimal." Avoid scope that forces a rewrite later.
+- MVP framing is disallowed. If there is doubt, default to MRP and durability.
+- Use MLP only when explicitly tied to UI/UX polish after the core is solid.
+
+## What Belongs Here
+- Multi-story outcomes that change core system behavior or architecture.
+- Cross-cutting initiatives that require multiple stories and tasks.
+- Policy or documentation programs that affect how we work or ship.
+
+## File Naming
+Use date-first, descriptive names:
+- `YYYY-MM-DD_<slug>_epic.md`
+
+Backlog location:
+- park non-active epics in `context_compass/tickets/epics/backlog/`.
+
+When completed, move to `context_compass/tickets/epics/completed/` and rename to:
+- `YYYY-MM-DD_<slug>_epic_completed.md`
+
+## How To Create An Epic (Deep, Not Minimal)
+1. Copy `context_compass/templates/epic_template.md`.
+2. Fill Metadata and keep `Status` and `Updated` current.
+3. Document Problem / Opportunity with concrete evidence and context.
+4. Write MRP Alignment as a durable, coherent core (not a quick experiment).
+5. Fill `Ticket Contract` (`ENTRY_GATE`, `EXECUTION_BOUNDARY`,
+   `DEPENDENCIES`, `EXIT_GATE`, `FAILURE_ESCALATION`).
+6. Define Goals, Non-Goals, Scope Boundaries, and Requirements.
+7. Record a `State Transition Event` for status changes.
+8. Add Success Metrics and Acceptance Criteria that are observable.
+9. Add Milestones with clear success criteria (`- [ ]` checkboxes required).
+10. List Stories required to complete the epic, each with an ID.
+11. Add Epic-level Tasks like "Complete story <STORY-ID>" to make progress explicit.
+12. Fill `Applicable Anti-Patterns` with program-level checks (not full catalog).
+13. Keep `Noting Behavior` focused on cross-story tradeoffs and sequencing.
+14. Add `Artifact Links (Optional)` only when the epic tracks concrete artifacts.
+15. Record artifact disposition (`delete_on_close`, `retain_as_reference`, or
+    `promote_to_documentation`) for linked artifacts.
+16. Record Risks / Mitigations, Validation plan, and Decision Log.
+17. Keep the Context / Handoff Summary current and specific (context is gold).
+
+## Depth Standard (No Handwaving)
+- Use concrete evidence and references (docs, code paths, diagrams).
+- Make assumptions explicit and list open questions.
+- Write so a future reader can resume without hidden knowledge.
+- Keep notes program-level; reference story/task notes for tactical evidence.
+
+## Completion Rules
+- Add completion header at the top of the file (see `context_compass/agent_onboarding/default/general/skills/workflow.md`).
+- Move the file to `context_compass/tickets/epics/completed/` with the `_completed` suffix.
+
+## References
+- `context_compass/SKILLS.MD` (deep descriptive model and naming rules)
+- `context_compass/agent_onboarding/default/general/skills/workflow.md` (ticket lifecycle and completion format)
+- `context_compass/templates/epic_template.md`
+
+
+
+

contextcompass_cli/_package/tickets/stories/README.md

@@ -0,0 +1,68 @@
+
+
+# Stories
+
+## Purpose
+Stories define a user- or system-facing slice of value within an epic. They translate an
+epic outcome into a coherent, testable unit of delivery that strengthens the MRP core.
+
+## MRP First (Required)
+- Every story must explain how it hardens or extends the core system.
+- MRP means "reasonable," not "minimal." Avoid scope that forces a rewrite later.
+- MVP framing is disallowed. Do not trade durability for speed.
+- MLP is allowed only when the story is explicitly about UI/UX polish.
+
+## What Belongs Here
+- A single, cohesive slice of value inside one epic.
+- A scope that can be completed by a small set of tasks with clear deliverables.
+
+## File Naming
+Use date-first, descriptive names:
+- `YYYY-MM-DD_<slug>_story.md`
+
+Backlog location:
+- park non-active stories in `context_compass/tickets/stories/backlog/`.
+
+When completed, move to `context_compass/tickets/stories/completed/` and rename to:
+- `YYYY-MM-DD_<slug>_story_completed.md`
+
+## How To Create A Story (Deep, Not Minimal)
+1. Copy `context_compass/templates/story_template.md`.
+2. Link the story to its epic in Metadata.
+3. Write a precise User Narrative with a concrete outcome.
+4. Explain Value / MRP Alignment with system-level impact.
+5. Fill `Ticket Contract` (`ENTRY_GATE`, `EXECUTION_BOUNDARY`,
+   `DEPENDENCIES`, `EXIT_GATE`, `FAILURE_ESCALATION`).
+6. Define Functional + Non-Functional requirements.
+7. Set Scope Boundaries and list Dependencies.
+8. Record a `State Transition Event` for status changes.
+9. Create a task checklist with explicit task IDs.
+10. Define Acceptance Criteria that are observable and testable.
+11. Add Validation / Test Plan and any UX/API/Data notes.
+12. Fill `Applicable Anti-Patterns` with lane-specific checks (not full catalog).
+13. Keep `Noting Behavior` aligned to cross-task synthesis notes.
+14. Add `Artifact Links (Optional)` when story work produces supporting
+    artifacts.
+15. Record artifact disposition (`delete_on_close`, `retain_as_reference`, or
+    `promote_to_documentation`) for linked artifacts.
+16. Record Risks / Mitigations, Decision Log, and keep Context / Handoff
+    Summary current.
+
+## Depth Standard (No Handwaving)
+- Cite relevant code paths, docs, or diagrams.
+- Make uncertainties and open questions explicit.
+- Write so a future reader can execute without additional context.
+- Keep notes synthesis-focused (task outcomes, dependency shifts, gate changes).
+
+## Completion Rules
+- Add completion header at the top of the file (see `context_compass/agent_onboarding/default/general/skills/workflow.md`).
+- Move the file to `context_compass/tickets/stories/completed/` with the `_completed` suffix.
+
+## References
+- `context_compass/SKILLS.MD` (deep descriptive model and naming rules)
+- `context_compass/agent_onboarding/default/general/skills/workflow.md` (ticket lifecycle and completion format)
+- `context_compass/templates/story_template.md`
+
+
+
+

contextcompass_cli/_package/tickets/tasks/README.md

@@ -0,0 +1,67 @@
+
+
+# Tasks
+
+## Purpose
+Tasks are the smallest actionable units that produce concrete deliverables. They must be
+precise, testable, and aligned with the MRP-first approach.
+
+## MRP First (Required)
+- Every task must contribute to a coherent, durable outcome.
+- MRP means "reasonable," not "minimal." Avoid scope that forces a rewrite later.
+- MVP shortcuts are disallowed. The task should not create debt that must be rewritten.
+- Use MLP only when a task is explicitly about UI/UX polish after core stability.
+
+## What Belongs Here
+- A single, concrete unit of work with clear scope and deliverables.
+- Work that can be validated and completed within a focused effort window.
+
+## File Naming
+Use date-first, descriptive names:
+- `YYYY-MM-DD_<slug>_task.md`
+
+Backlog location:
+- park non-active tasks in `context_compass/tickets/tasks/backlog/`.
+
+When completed, move to `context_compass/tickets/tasks/completed/` and rename to:
+- `YYYY-MM-DD_<slug>_task_completed.md`
+
+## How To Create A Task (Deep, Not Minimal)
+1. Copy `context_compass/templates/task_template.md`.
+2. Link the task to its story in Metadata.
+3. Write a concrete Objective that defines the smallest meaningful outcome.
+4. Fill `Ticket Contract` (`ENTRY_GATE`, `EXECUTION_BOUNDARY`,
+   `DEPENDENCIES`, `EXIT_GATE`, `FAILURE_ESCALATION`).
+5. Define Scope Boundaries (in scope / out of scope) to prevent creep.
+6. Record a `State Transition Event` for status changes.
+7. List Steps / Checklist with clear, ordered actions.
+8. Define Deliverables and Files / Paths Impacted.
+9. Record Validation status and recommended commands (or "Not run").
+10. Capture Risks / Rollback Notes if relevant.
+11. Fill `Applicable Anti-Patterns` with lane-specific checks (do not paste the
+    full catalog).
+12. Keep `Noting Behavior` aligned to tactical task-level notes and update
+    `## Notes` on each meaningful finding.
+13. Add `Artifact Links (Optional)` when the task creates supporting artifacts.
+14. Record artifact disposition (`delete_on_close`, `retain_as_reference`, or
+    `promote_to_documentation`) and closure trigger for each linked artifact.
+15. Complete the Done Checklist and keep Context / Handoff Summary current.
+
+## Depth Standard (No Handwaving)
+- Be explicit about what will change and why.
+- Reference relevant files, docs, or diagrams.
+- Record open questions or blockers immediately.
+- Keep notes tactical: concrete finding -> impact -> one-step next action.
+- Keep anti-pattern enforcement lightweight: lane-specific checklist only.
+
+## Completion Rules
+- Add completion header at the top of the file (see `context_compass/agent_onboarding/default/general/skills/workflow.md`).
+- Move the file to `context_compass/tickets/tasks/completed/` with the `_completed` suffix.
+
+## References
+- `context_compass/SKILLS.MD` (deep descriptive model and naming rules)
+- `context_compass/agent_onboarding/default/general/skills/workflow.md` (ticket lifecycle and completion format)
+- `context_compass/templates/task_template.md`
+
+
+