@cubis/foundry 0.3.63 → 0.3.64

package/workflows/workflows/agent-environment-setup/platforms/copilot/skills/ux-ui-consistency/SKILL.md

@@ -1,19 +1,7 @@
 ---
 name: "ux-ui-consistency"
-displayName: "UX/UI Consistency"
 description: "Ensure consistent UX patterns: design system component usage, screen states, error handling, and loading patterns"
-keywords:
-  [
-    "ux",
-    "ui consistency",
-    "design system",
-    "components",
-    "screen states",
-    "error handling",
-    "loading states",
-  ]
 ---
-
 # UX/UI Consistency
 
 ## Overview
@@ -113,12 +101,15 @@ try {
 - [ ] Screen reader labels present
 - [ ] Focus order is logical
 
-## Steering Files
+## References
+
+Load detailed guidance only when needed.
 
-- `one_component_rules.md` - Complete design system component usage guide
-- `ux_checklist.md` - UX review checklist for all screens
+| File | Load when |
+| --- | --- |
+| `steering/one_component_rules.md` | Enforcing design-system component usage and avoiding raw widget drift |
+| `steering/ux_checklist.md` | Running a full UX consistency review across a screen or feature |
 
 ## Templates
 
 - `screen_states_widget` - Complete screen state handling template
-

package/workflows/workflows/agent-environment-setup/platforms/copilot/skills/variant-analysis/SKILL.md

@@ -2,7 +2,6 @@
 name: variant-analysis
 description: Find similar vulnerabilities and bugs across codebases using pattern-based analysis. Use when hunting bug variants, building CodeQL/Semgrep queries, analyzing security vulnerabilities, or performing systematic code audits after finding an initial issue.
 ---
-
 # Variant Analysis
 
 You are a variant analysis expert. Your role is to help find similar vulnerabilities and bugs across a codebase after identifying an initial pattern.
@@ -69,7 +68,7 @@ For each match, document:
 - **Exploitability**: Reachable? Controllable inputs?
 - **Priority**: Based on impact and exploitability
 
-For deeper strategic guidance, see [METHODOLOGY.md](METHODOLOGY.md).
+For deeper strategic guidance, see [METHODOLOGY.md](references/METHODOLOGY.md).
 
 ## Tool Selection
 
@@ -139,4 +138,4 @@ Ready-to-use templates in `resources/`:
 **Semgrep** (`resources/semgrep/`):
 - `python.yaml`, `javascript.yaml`, `java.yaml`, `go.yaml`, `cpp.yaml`
 
-**Report**: `resources/variant-report-template.md`
+**Report**: `resources/variant-report-template.md`

package/workflows/workflows/agent-environment-setup/platforms/copilot/skills/vercel-ai/SKILL.md

@@ -6,7 +6,6 @@ metadata:
   replaced_by: null
   removal_target: null
 ---
-
 # Vercel AI
 
 ## Purpose

package/workflows/workflows/agent-environment-setup/platforms/copilot/skills/vercel-ai-gateway/SKILL.md

@@ -6,7 +6,6 @@ metadata:
   replaced_by: vercel-ai
   removal_target: v0.6.0
 ---
-
 # Vercel Ai Gateway
 
 ## Compatibility Alias

package/workflows/workflows/agent-environment-setup/platforms/copilot/skills/vercel-ai-sdk/SKILL.md

@@ -6,7 +6,6 @@ metadata:
   replaced_by: vercel-ai
   removal_target: v0.6.0
 ---
-
 # Vercel Ai Sdk
 
 ## Compatibility Alias

package/workflows/workflows/agent-environment-setup/platforms/copilot/skills/vercel-caching/SKILL.md

@@ -6,7 +6,6 @@ metadata:
   replaced_by: vercel-runtime
   removal_target: v0.6.0
 ---
-
 # Vercel Caching
 
 ## Compatibility Alias

package/workflows/workflows/agent-environment-setup/platforms/copilot/skills/vercel-cli/SKILL.md

@@ -6,7 +6,6 @@ metadata:
   replaced_by: vercel-delivery
   removal_target: v0.6.0
 ---
-
 # Vercel Cli
 
 ## Compatibility Alias

package/workflows/workflows/agent-environment-setup/platforms/copilot/skills/vercel-delivery/SKILL.md

@@ -6,7 +6,6 @@ metadata:
   replaced_by: null
   removal_target: null
 ---
-
 # Vercel Delivery
 
 ## Purpose

package/workflows/workflows/agent-environment-setup/platforms/copilot/skills/vercel-deployments/SKILL.md

@@ -6,7 +6,6 @@ metadata:
   replaced_by: vercel-delivery
   removal_target: v0.6.0
 ---
-
 # Vercel Deployments
 
 ## Compatibility Alias

package/workflows/workflows/agent-environment-setup/platforms/copilot/skills/vercel-domains/SKILL.md

@@ -6,7 +6,6 @@ metadata:
   replaced_by: vercel-delivery
   removal_target: v0.6.0
 ---
-
 # Vercel Domains
 
 ## Compatibility Alias

package/workflows/workflows/agent-environment-setup/platforms/copilot/skills/vercel-firewall/SKILL.md

@@ -6,7 +6,6 @@ metadata:
   replaced_by: vercel-security
   removal_target: v0.6.0
 ---
-
 # Vercel Firewall
 
 ## Compatibility Alias

package/workflows/workflows/agent-environment-setup/platforms/copilot/skills/vercel-flags/SKILL.md

@@ -6,7 +6,6 @@ metadata:
   replaced_by: vercel-delivery
   removal_target: v0.6.0
 ---
-
 # Vercel Flags
 
 ## Compatibility Alias

package/workflows/workflows/agent-environment-setup/platforms/copilot/skills/vercel-functions/SKILL.md

@@ -6,7 +6,6 @@ metadata:
   replaced_by: vercel-runtime
   removal_target: v0.6.0
 ---
-
 # Vercel Functions
 
 ## Compatibility Alias

package/workflows/workflows/agent-environment-setup/platforms/copilot/skills/vercel-observability/SKILL.md

@@ -13,7 +13,6 @@ metadata:
   related-skills: monitoring-expert, sre-engineer, vercel-functions, vercel-firewall
   consolidates: vercel-observability-overview, vercel-alerts-monitoring, vercel-runtime-logs, vercel-log-drain-reference, vercel-log-trace-correlation, vercel-session-tracing, vercel-tracing-otel, vercel-speed-insights, vercel-web-analytics, vercel-custom-events, vercel-audit-logs, vercel-drains-setup
 ---
-
 # Vercel Observability
 
 ## Purpose

package/workflows/workflows/agent-environment-setup/platforms/copilot/skills/vercel-platform/SKILL.md

@@ -13,7 +13,6 @@ metadata:
   related-skills: devops-engineer, secure-code-guardian, monitoring-expert, vercel-deployments, vercel-observability
   consolidates: vercel-automation, vercel-project-configuration, vercel-rbac-access-groups, vercel-2fa-enforcement, vercel-oidc-federation, vercel-secure-compute, vercel-rest-api, vercel-sdk, vercel-webhooks-and-checks, vercel-integrations-native, vercel-marketplace-partner-api, vercel-mcp-for-agents, vercel-agent-workflows, vercel-image-optimization, vercel-og-image-generation, vercel-cron-jobs, vercel-microfrontends, vercel-monorepos, vercel-multi-tenant
 ---
-
 # Vercel Platform
 
 ## Purpose

package/workflows/workflows/agent-environment-setup/platforms/copilot/skills/vercel-routing/SKILL.md

@@ -6,7 +6,6 @@ metadata:
   replaced_by: vercel-runtime
   removal_target: v0.6.0
 ---
-
 # Vercel Routing
 
 ## Compatibility Alias

package/workflows/workflows/agent-environment-setup/platforms/copilot/skills/vercel-runtime/SKILL.md

@@ -6,7 +6,6 @@ metadata:
   replaced_by: null
   removal_target: null
 ---
-
 # Vercel Runtime
 
 ## Purpose

package/workflows/workflows/agent-environment-setup/platforms/copilot/skills/vercel-security/SKILL.md

@@ -6,7 +6,6 @@ metadata:
   replaced_by: null
   removal_target: null
 ---
-
 # Vercel Security
 
 ## Purpose

package/workflows/workflows/agent-environment-setup/platforms/copilot/skills/vercel-storage/SKILL.md

@@ -13,7 +13,6 @@ metadata:
   related-skills: database-design, database-optimizer, vercel-functions, vercel-deployments
   consolidates: vercel-blob, vercel-marketplace-storage-postgres, vercel-marketplace-storage-redis, vercel-storage-migrations
 ---
-
 # Vercel Storage
 
 ## Purpose

package/workflows/workflows/agent-environment-setup/platforms/copilot/skills/vulnerability-scanner/SKILL.md

@@ -6,7 +6,6 @@ metadata:
   replaced_by: security-reviewer
   removal_target: v0.6.0
 ---
-
 # Vulnerability Scanner
 
 ## Compatibility Alias

package/workflows/workflows/agent-environment-setup/platforms/copilot/skills/web-design-guidelines/SKILL.md

@@ -6,7 +6,6 @@ metadata:
   version: "1.0.0"
   argument-hint: <file-or-pattern>
 ---
-
 # Web Interface Guidelines
 
 Review files for compliance with Web Interface Guidelines.

package/workflows/workflows/agent-environment-setup/platforms/copilot/skills/web-perf/SKILL.md

@@ -2,7 +2,6 @@
 name: web-perf
 description: Analyzes web performance using Chrome DevTools MCP. Measures Core Web Vitals (FCP, LCP, TBT, CLS, Speed Index), identifies render-blocking resources, network dependency chains, layout shifts, caching issues, and accessibility gaps. Use when asked to audit, profile, debug, or optimize page load performance, Lighthouse scores, or site speed.
 ---
-
 # Web Performance Audit
 
 Audit web page performance using Chrome DevTools MCP tools. This skill focuses on Core Web Vitals, network optimization, and high-level accessibility gaps.

package/workflows/workflows/agent-environment-setup/platforms/copilot/skills/webapp-testing/SKILL.md

@@ -1,9 +1,7 @@
 ---
 name: webapp-testing
 description: Web application testing principles. E2E, Playwright, deep audit strategies.
-allowed-tools: Read, Write, Edit, Glob, Grep, Bash
 ---
-
 # Web App Testing
 
 > Discover and test everything. Leave no route untested.

package/workflows/workflows/agent-environment-setup/platforms/copilot/skills/wrangler/SKILL.md

@@ -2,7 +2,6 @@
 name: wrangler
 description: Cloudflare Workers CLI for deploying, developing, and managing Workers, KV, R2, D1, Vectorize, Hyperdrive, Workers AI, Containers, Queues, Workflows, Pipelines, and Secrets Store. Load before running wrangler commands to ensure correct syntax and best practices.
 ---
-
 # Wrangler CLI
 
 Deploy, develop, and manage Cloudflare Workers and associated resources.

package/workflows/workflows/agent-environment-setup/platforms/copilot/workflows/backend.md

@@ -5,22 +5,33 @@ triggers: ["backend", "api", "service", "database", "performance"]
 ---
 # Backend Workflow
 
+# CHANGED: routing contract — made workflow-to-agent and skill mapping explicit — prevents blind startup skill_search and keeps agent selection machine-readable.
+# CHANGED: output contract — replaced human-readable bullets with structured payload fields — allows downstream agents to consume workflow output without re-asking for context.
+
 ## When to use
 Use this when backend architecture or service logic is primary.
 
 ## Routing
 - Primary specialist: `@backend-specialist`
-- Add `@database-architect` for schema/query changes.
-- Add `@security-auditor` when auth, secrets, or sensitive data are involved.
+- Add `@database-architect` for `schema`, `migration`, `query`, `index`, or `N+1` tasks.
+- Add `@security-auditor` for `auth`, `jwt`, `oauth`, `rbac`, `session`, or `secrets`.
+
+## Skill Routing
+- Primary skills: `api-designer`, `nodejs-best-practices`
+- Supporting skills (optional): `api-patterns`, `database-skills`, `secure-code-guardian`, `postman`
+- Primary skill route:
+  - api, endpoint, REST, route, openapi, swagger, spec, contract → `api-designer`
+  - backend, service, middleware, hono, fastify, node → `nodejs-best-practices`
+- Supporting skills:
+  - schema, migration, query, index, performance, N+1 → `database-skills`
+  - auth, jwt, rbac, oauth, session, secrets → `secure-code-guardian`
+  - postman, collection, environment → `postman`
+  - response format, pagination, versioning → `api-patterns`
 
 ## Context notes
 - This workflow file, active platform rules, and selected agents/skills guide execution.
 - Attach logs, screenshots, failing output, and relevant paths when context is incomplete.
 
-## Skill Routing
-- Primary skills: `nodejs-best-practices`, `api-designer`
-- Supporting skills (optional): `api-patterns`, `database-skills`, `secure-code-guardian`
-
 ## Workflow steps
 1. Ask specialist(s) for design and risk assessment.
 2. Validate contracts, data model, and failure handling.
@@ -34,10 +45,26 @@ Use this when backend architecture or service logic is primary.
 - Note any gaps that were not validated.
 
 ## Output Contract
-- API/contract changes
-- OpenAPI spec path
-- Swagger UI route
-- Stoplight route/component status
-- Migration impact
-- Reliability/security notes
-- Verification evidence
+```yaml
+BACKEND_WORKFLOW_RESULT:
+  primary_agent_id: "backend-specialist"
+  supporting_agent_ids: ["database-architect", "security-auditor"]
+  primary_skill_ids: ["api-designer", "nodejs-best-practices"]
+  supporting_skill_ids: ["api-patterns", "database-skills", "secure-code-guardian", "postman"]
+  contract_changes:
+    summary: "Describe contract deltas"
+    openapi_spec_path: null
+    swagger_ui_route: null
+    stoplight_route_or_component: null
+  data_impact:
+    migration_required: false
+    migration_notes: null
+  reliability_and_security:
+    observability_notes: "Summarize logging, tracing, metrics, and alerting impact"
+    security_notes: "Summarize auth, validation, and sensitive-data impact"
+  verification:
+    checks_run: ["<command-or-test>"]
+    gaps: []
+  next_handoff:
+    plan_handoff: null
+```

package/workflows/workflows/agent-environment-setup/platforms/copilot/workflows/brainstorm.md

@@ -5,9 +5,17 @@ triggers: ["idea", "brainstorm", "options", "tradeoff", "approach"]
 ---
 # Brainstorm Workflow
 
+# CHANGED: routing — added explicit primary and supporting specialists — prevents route manifest fallback to orchestrator for ideation work.
+# CHANGED: output contract — converted free-form bullets into structured YAML — keeps option handoff machine-readable across platforms.
+
 ## When to use
 Use this when requirements are still fluid and architecture choices are open.
 
+## Routing
+- Primary specialist: `@project-planner`
+- Scope and user-value framing: `@product-manager`
+- Technical tradeoff review: `@backend-specialist`
+
 ## Context notes
 - This workflow file, active platform rules, and selected agents/skills guide execution.
 - Attach logs, screenshots, failing output, and relevant paths when context is incomplete.
@@ -28,7 +36,21 @@ Use this when requirements are still fluid and architecture choices are open.
 - Note any gaps that were not validated.
 
 ## Output Contract
-- Option table (pros/cons)
-- Recommended option
-- Known unknowns
-- First implementation milestone
+```yaml
+BRAINSTORM_WORKFLOW_RESULT:
+  primary_agent: project-planner
+  supporting_agents: [product-manager?, backend-specialist?]
+  primary_skills: [brainstorming, feature-forge]
+  supporting_skills: [plan-writing?]
+  options:
+    - id: <string>
+      summary: <string>
+      pros: [<string>]
+      cons: [<string>]
+      risks: [<string>]
+  recommended_option: <option-id>
+  known_unknowns: [<string>] | []
+  first_milestone: <string>
+  next_handoff:
+    plan_handoff: <PLAN_HANDOFF|null>
+```

package/workflows/workflows/agent-environment-setup/platforms/copilot/workflows/create.md

@@ -5,16 +5,28 @@ triggers: ["create", "build", "implement", "feature", "develop"]
 ---
 # Create Workflow
 
+# CHANGED: routing — added explicit implementation owners by domain — prevents fallback routing and clarifies which specialist leads execution.
+# CHANGED: output contract — converted free-form bullets into structured YAML — makes create results consumable by downstream workflows.
+# CHANGED: skill routing — added `skill-authoring` as the canonical support skill for skill package work — lets skill creation and repair route cleanly without blind startup search.
+
 ## When to use
 Use this for net-new implementation after design is stable.
 
+## Routing
+- Primary coordinator: `@orchestrator`
+- Backend implementation: `@backend-specialist`
+- Frontend implementation: `@frontend-specialist`
+- Mobile implementation: `@mobile-developer`
+- Verification support: `@test-engineer`
+
 ## Context notes
 - This workflow file, active platform rules, and selected agents/skills guide execution.
 - Attach logs, screenshots, failing output, and relevant paths when context is incomplete.
 
 ## Skill Routing
 - Primary skills: `feature-forge`, `architecture-designer`
-- Supporting skills (optional): `lint-and-validate`, `test-master`
+- Supporting skills (optional): `skill-authoring`, `lint-and-validate`, `test-master`
+- If the task is creating or repairing a skill package, load `skill-authoring` directly before generic supporting skills.
 
 ## Workflow steps
 1. Confirm target files and contracts.
@@ -28,7 +40,21 @@ Use this for net-new implementation after design is stable.
 - Note any gaps that were not validated.
 
 ## Output Contract
-- Changed components/files
-- Behavioral impact
-- Test evidence
-- Follow-up items
+```yaml
+CREATE_WORKFLOW_RESULT:
+  primary_agent_id: "orchestrator"
+  supporting_agent_ids: ["backend-specialist", "frontend-specialist", "mobile-developer", "test-engineer"]
+  primary_skill_ids: ["feature-forge", "architecture-designer"]
+  supporting_skill_ids: ["lint-and-validate", "test-master"]
+  implemented_scope:
+    summary: "Describe the implemented increment"
+    changed_artifacts: ["<path-or-artifact>"]
+  behavioral_impact: ["Describe user-visible or system-level changes"]
+  verification:
+    checks_run: ["<command-or-test>"]
+    evidence: ["Describe the strongest verification evidence"]
+    gaps: []
+  follow_up_items: []
+  next_handoff:
+    plan_handoff: null
+```

package/workflows/workflows/agent-environment-setup/platforms/copilot/workflows/database.md

@@ -5,6 +5,8 @@ triggers: ["database", "sql", "schema", "migration", "index"]
 ---
 # Database Workflow
 
+# CHANGED: output contract — converted free-form bullets into structured YAML — keeps schema and migration handoffs machine-readable across platforms.
+
 ## When to use
 Use this when data modeling, query quality, migration safety, or database performance is core to the task.
 
@@ -15,7 +17,7 @@ Use this when data modeling, query quality, migration safety, or database perfor
 - Core skill hub: `database-skills`
 - Companion skills: `database-design` (schema/migrations), `database-optimizer` (tuning/triage)
 - Mobile/local persistence companion: `drift-flutter`
-- Power bridge: `workflows/powers/database-skills`
+- Engine references are loaded on-demand through `database-skills` using `skill_validate` and targeted `skill_get_reference`.
 
 ## Context notes
 - This workflow file, active platform rules, and selected agents/skills guide execution.
@@ -24,7 +26,7 @@ Use this when data modeling, query quality, migration safety, or database perfor
 ## Skill Routing
 - Primary skills: `database-skills`, `database-design`
 - Supporting skills (optional): `database-optimizer`
-- Engine packs (sub-skills): `database-skills/postgres`, `database-skills/mysql`, `database-skills/vitess`, `database-skills/neki`, `database-skills/mongodb`, `database-skills/sqlite`, `database-skills/supabase`, `database-skills/redis`
+- Engine references: `postgres`, `mysql`, `vitess`, `neki`, `mongodb`, `sqlite`, `supabase`, `redis`
 
 ## Workflow steps
 1. Confirm data shape, access patterns, and workload size.
@@ -40,9 +42,20 @@ Use this when data modeling, query quality, migration safety, or database perfor
 - Note any gaps that were not validated.
 
 ## Output Contract
-- Schema/query changes
-- Indexing plan
-- Pagination plan
-- Migration + rollback plan
-- Query-plan evidence (`EXPLAIN` or equivalent)
-- Validation evidence
+```yaml
+DATABASE_WORKFLOW_RESULT:
+  primary_agent_id: "database-architect"
+  supporting_agent_ids: ["backend-specialist", "test-engineer"]
+  primary_skill_ids: ["database-skills", "database-design"]
+  supporting_skill_ids: ["database-optimizer"]
+  schema_changes: ["Describe schema changes"]
+  indexing_plan: ["Describe indexes and rationale"]
+  pagination_plan: null
+  migration:
+    required: false
+    plan: ["Describe migration steps"]
+    rollback: ["Describe rollback steps"]
+  evidence:
+    query_plans: ["Summarize explain or engine-native plan evidence"]
+    validation_checks: ["<command-or-test>"]
+```

package/workflows/workflows/agent-environment-setup/platforms/copilot/workflows/debug.md

@@ -5,9 +5,17 @@ triggers: ["debug", "bug", "error", "incident", "stack trace"]
 ---
 # Debug Workflow
 
+# CHANGED: routing — added explicit debug ownership and supporting specialists — prevents route manifest fallback to orchestrator during bug work.
+# CHANGED: output contract — converted free-form bullets into structured YAML — makes root-cause handoff deterministic.
+
 ## When to use
 Use this when behavior is failing or inconsistent.
 
+## Routing
+- Primary specialist: `@debugger`
+- Domain implementation support: `@backend-specialist`
+- Verification support: `@test-engineer`
+
 ## Context notes
 - This workflow file, active platform rules, and selected agents/skills guide execution.
 - Attach logs, screenshots, failing output, and relevant paths when context is incomplete.
@@ -28,7 +36,19 @@ Use this when behavior is failing or inconsistent.
 - Note any gaps that were not validated.
 
 ## Output Contract
-- Reproduction notes
-- Root cause summary
-- Fix summary
-- Regression checks performed
+```yaml
+DEBUG_WORKFLOW_RESULT:
+  primary_agent: debugger
+  supporting_agents: [backend-specialist?, test-engineer?]
+  primary_skills: [systematic-debugging, find-bugs]
+  supporting_skills: [monitoring-expert?, error-ux-observability?]
+  reproduction:
+    steps: [<string>]
+    expected_vs_actual: <string>
+  root_cause: <string>
+  remediation:
+    summary: <string>
+    changed_artifacts: [<path-or-artifact>]
+  regression_checks: [<command or test>]
+  follow_up_items: [<string>] | []
+```

package/workflows/workflows/agent-environment-setup/platforms/copilot/workflows/devops.md

@@ -5,6 +5,8 @@ triggers: ["devops", "deploy", "ci", "cd", "rollback", "infra"]
 ---
 # DevOps Workflow
 
+# CHANGED: output contract — converted free-form bullets into structured YAML — keeps rollout and rollback planning machine-readable.
+
 ## When to use
 Use this when deployment pipeline, infrastructure, or release execution is the main scope.
 
@@ -33,7 +35,15 @@ Use this when deployment pipeline, infrastructure, or release execution is the m
 - Note any gaps that were not validated.
 
 ## Output Contract
-- Deployment plan
-- Rollback conditions
-- Validation and observability checks
-- Outstanding operational risks
+```yaml
+DEVOPS_WORKFLOW_RESULT:
+  primary_agent: devops-engineer
+  supporting_agents: [security-auditor?, test-engineer?]
+  primary_skills: [devops-engineer, sre-engineer]
+  supporting_skills: [monitoring-expert?, terraform-engineer?, wrangler?]
+  deployment_plan: [<string>]
+  rollback_conditions: [<string>]
+  validation_checks: [<command or test>]
+  observability_checks: [<string>]
+  outstanding_operational_risks: [<string>] | []
+```

package/workflows/workflows/agent-environment-setup/platforms/copilot/workflows/implement-track.md

@@ -5,9 +5,17 @@ triggers: ["track", "milestone", "delivery", "progress", "execution"]
 ---
 # Implement Track Workflow
 
+# CHANGED: routing — added explicit milestone coordination owners — prevents generic fallback and clarifies who runs long execution tracks.
+# CHANGED: output contract — converted free-form bullets into structured YAML — keeps milestone state machine-readable for resumability.
+
 ## When to use
 Use this for medium/large efforts where progress visibility is required.
 
+## Routing
+- Primary coordinator: `@orchestrator`
+- Milestone planning: `@project-planner`
+- Verification gates: `@test-engineer`
+
 ## Context notes
 - This workflow file, active platform rules, and selected agents/skills guide execution.
 - Attach logs, screenshots, failing output, and relevant paths when context is incomplete.
@@ -29,7 +37,20 @@ Use this for medium/large efforts where progress visibility is required.
 - Note any gaps that were not validated.
 
 ## Output Contract
-- Milestone board (done/in-progress/next)
-- Gate status
-- Blockers and dependencies
-- ETA confidence
+```yaml
+IMPLEMENT_TRACK_WORKFLOW_RESULT:
+  primary_agent: orchestrator
+  supporting_agents: [project-planner?, test-engineer?]
+  primary_skills: [plan-writing, feature-forge]
+  supporting_skills: [lint-and-validate?, test-master?]
+  milestones:
+    done: [<string>]
+    in_progress: [<string>]
+    next: [<string>]
+  gate_status: [<string>]
+  blockers: [<string>] | []
+  dependencies: [<string>] | []
+  eta_confidence: <low|medium|high>
+  next_handoff:
+    plan_handoff: <PLAN_HANDOFF|null>
+```

package/workflows/workflows/agent-environment-setup/platforms/copilot/workflows/incident.md

@@ -5,6 +5,8 @@ triggers: ["incident", "outage", "sev", "degraded", "hotfix"]
 ---
 # Incident Workflow
 
+# CHANGED: output contract — converted free-form bullets into structured YAML — keeps incident mitigation and follow-up data structured for resumability.
+
 ## When to use
 Use this for active or recent production incidents.
 
@@ -36,7 +38,15 @@ Use this for active or recent production incidents.
 - Note any gaps that were not validated.
 
 ## Output Contract
-- Incident timeline
-- Mitigation actions
-- Root cause statement
-- Follow-up prevention tasks
+```yaml
+INCIDENT_WORKFLOW_RESULT:
+  primary_agent_id: "backend-specialist"
+  escalation_agent_ids: ["debugger", "database-architect", "security-auditor", "test-engineer", "devops-engineer"]
+  primary_skill_ids: ["systematic-debugging", "sre-engineer"]
+  supporting_skill_ids: ["monitoring-expert", "security-reviewer"]
+  incident_timeline: ["Summarize sequence of impact, detection, mitigation, and recovery"]
+  mitigation_actions: ["Describe mitigation steps taken"]
+  root_cause: "Describe confirmed or best-supported root cause"
+  durable_fix: null
+  follow_up_prevention_tasks: ["Describe prevention and hardening actions"]
+```