Enhance autopilot documentation and workflows: Add assumptions regarding single project per workspace, update notification sound references, and introduce context budget heuristics for managing session limits. Revise various skill documents to reflect changes in task management, including ticketing and testing processes, ensuring clarity and consistency across the system.

.cursor/skills/plan/steps/06_jira-epics.md

@@ -1,13 +1,13 @@
-## Step 6: Jira Epics
+## Step 6: Work Item Epics
 
 **Role**: Professional product manager
 
-**Goal**: Create Jira epics from components, ordered by dependency
+**Goal**: Create epics from components, ordered by dependency
 
-**Constraints**: Epic descriptions must be **comprehensive and self-contained** — a developer reading only the Jira epic should understand the full context without needing to open separate files.
+**Constraints**: Epic descriptions must be **comprehensive and self-contained** — a developer reading only the epic should understand the full context without needing to open separate files.
 
 1. **Create "Bootstrap & Initial Structure" epic first** — this epic will parent the `01_initial_structure` task created by the decompose skill. It covers project scaffolding: folder structure, shared models, interfaces, stubs, CI/CD config, DB migrations setup, test structure.
-2. Generate Jira Epics for each component using Jira MCP, structured per `templates/epic-spec.md`
+2. Generate epics for each component using the configured work item tracker (Jira MCP or Azure DevOps MCP — see `autopilot/protocols.md`), structured per `templates/epic-spec.md`
 3. Order epics by dependency (Bootstrap epic is always first, then components based on their dependency graph)
 4. Include effort estimation per epic (T-shirt size or story points range)
 5. Ensure each epic has clear acceptance criteria cross-referenced with component specs
@@ -15,7 +15,7 @@
 
 **CRITICAL — Epic description richness requirements**:
 
-Each epic description in Jira MUST include ALL of the following sections with substantial content:
+Each epic description MUST include ALL of the following sections with substantial content:
 - **System context**: where this component fits in the overall architecture (include Mermaid diagram showing this component's position and connections)
 - **Problem / Context**: what problem this component solves, why it exists, current pain points
 - **Scope**: detailed in-scope and out-of-scope lists
@@ -31,7 +31,7 @@ Each epic description in Jira MUST include ALL of the following sections with su
 - **Key constraints**: from restrictions.md that affect this component
 - **Testing strategy**: summary of test types and coverage from tests.md
 
-Do NOT create minimal epics with just a summary and short description. The Jira epic is the primary reference document for the implementation team.
+Do NOT create minimal epics with just a summary and short description. The epic is the primary reference document for the implementation team.
 
 **Self-verification**:
 - [ ] "Bootstrap & Initial Structure" epic exists and is first in order
@@ -45,4 +45,4 @@ Do NOT create minimal epics with just a summary and short description. The Jira
 
 7. **Create "Blackbox Tests" epic** — this epic will parent the blackbox test tasks created by the `/decompose` skill. It covers implementing the test scenarios defined in `tests/`.
 
-**Save action**: Epics created in Jira via MCP. Also saved locally in `epics.md` with Jira IDs.
+**Save action**: Epics created via the configured tracker MCP. Also saved locally in `epics.md` with ticket IDs. If `tracker: local`, save locally only.

.cursor/skills/plan/templates/epic-spec.md

@@ -1,6 +1,6 @@
-# Jira Epic Template
+# Epic Template
 
-Use this template for each Jira epic. Create epics via Jira MCP.
+Use this template for each epic. Create epics via the configured work item tracker (Jira MCP or Azure DevOps MCP).
 
 ---