@cubis/foundry 0.3.82 → 0.3.83

package/workflows/workflows/agent-environment-setup/platforms/{antigravity/workflows/implement-track.md → copilot/prompts/implement-track.prompt.md}

@@ -1,9 +1,20 @@
----
-command: "/implement-track"
-description: "Execute large work in milestones with explicit quality gates and status updates."
-triggers: ["track", "milestone", "delivery", "progress", "execution"]
----
-
+# Workflow Prompt: /implement-track
+
+Execute large work in milestones with explicit quality gates and status updates.
+
+Execution contract:
+1. Treat route selection as already resolved by this command; do not begin with skill discovery.
+2. Read `docs/foundation/PRODUCT.md`, `ENGINEERING_RULES.md`, `docs/foundation/ARCHITECTURE.md`, and `docs/foundation/TECH.md` in that order when they exist before non-trivial execution.
+Attached skills:
+- Load these exact skill IDs first: `system-design`, `api-design`, `database-design`, `typescript-best-practices`, `javascript-best-practices`, `python-best-practices`, `golang-best-practices`, `react`, `nextjs`.
+- Local skill file hints if installed: `.github/skills/system-design/SKILL.md`, `.github/skills/api-design/SKILL.md`, `.github/skills/database-design/SKILL.md`, `.github/skills/typescript-best-practices/SKILL.md`, `.github/skills/javascript-best-practices/SKILL.md`, `.github/skills/python-best-practices/SKILL.md`, `.github/skills/golang-best-practices/SKILL.md`, `.github/skills/react/SKILL.md`.
+- Treat the skill bundle as already resolved for this workflow. Do not start with route discovery.
+3. Apply workflow sections in order: When to use, Workflow steps, Context notes, Verification.
+4. Route to the workflow's primary specialist and only add supporting specialists when needed.
+5. If freshness or public comparison matters, run `deep-research` before implementation and use official docs as primary evidence.
+6. Return actions taken, verification evidence, and any gaps.
+
+Workflow source:
 # Implement Track Workflow
 
 ## When to use
@@ -12,9 +23,9 @@ Use this for large-scale implementation work that spans multiple sessions or mil
 
 ## Routing
 
-- Primary coordinator: `.agent/agents/orchestrator`
+- Primary coordinator: `@orchestrator`
 - Implementation agents: determined by task domain
-- Quality gate: `.agent/agents/validator`
+- Quality gate: `@validator`
 
 ## Context notes
 
@@ -26,7 +37,7 @@ Use this for large-scale implementation work that spans multiple sessions or mil
 ## Skill Routing
 
 - Primary skills: `system-design`, `api-design`
-- Supporting skills (optional): `database-design`, `typescript-best-practices`, `javascript-best-practices`, `python-best-practices`, `golang-best-practices`, `react`, `nextjs`
+- Supporting skills (optional): `database-design`, `typescript-pro`, `javascript-pro`, `python-pro`, `golang-pro`, `react-expert`, `nextjs-developer`
 - Start with `system-design` for milestone planning. Load domain-specific skills per milestone based on implementation needs.
 
 ## Workflow steps
@@ -52,7 +63,7 @@ IMPLEMENT_TRACK_WORKFLOW_RESULT:
   primary_agent: orchestrator
   supporting_agents: [<milestone-agents>]
   primary_skills: [system-design, api-design]
-  supporting_skills: [database-design?, typescript-best-practices?, javascript-best-practices?, python-best-practices?, golang-best-practices?, react?, nextjs?]
+  supporting_skills: [database-design?, typescript-pro?, javascript-pro?, python-pro?, golang-pro?, react-expert?, nextjs-developer?]
   milestones:
     - id: <milestone-id>
       description: <string>
@@ -67,5 +78,3 @@ IMPLEMENT_TRACK_WORKFLOW_RESULT:
   doc_impact: none | tech | rules | both
   follow_up_items: [<string>] | []
 ```
-
-> **Antigravity note:** Use Agent Manager for parallel agent coordination. Workflow files are stored under `.agent/workflows/`.

package/workflows/workflows/agent-environment-setup/platforms/copilot/prompts/migrate.prompt.md

@@ -0,0 +1,79 @@
+# Workflow Prompt: /migrate
+
+Plan and execute technology migrations, framework upgrades, and dependency updates with rollback safety, incremental verification, and zero-downtime transition.
+
+Execution contract:
+1. Treat route selection as already resolved by this command; do not begin with skill discovery.
+2. Read `docs/foundation/PRODUCT.md`, `ENGINEERING_RULES.md`, `docs/foundation/ARCHITECTURE.md`, and `docs/foundation/TECH.md` in that order when they exist before non-trivial execution.
+Attached skills:
+- Load these exact skill IDs first: `system-design`, `code-review`, `unit-testing`, `typescript-best-practices`, `javascript-best-practices`, `python-best-practices`, `golang-best-practices`.
+- Local skill file hints if installed: `.github/skills/system-design/SKILL.md`, `.github/skills/code-review/SKILL.md`, `.github/skills/unit-testing/SKILL.md`, `.github/skills/typescript-best-practices/SKILL.md`, `.github/skills/javascript-best-practices/SKILL.md`, `.github/skills/python-best-practices/SKILL.md`, `.github/skills/golang-best-practices/SKILL.md`.
+- Treat the skill bundle as already resolved for this workflow. Do not start with route discovery.
+3. Apply workflow sections in order: When to use, Workflow steps, Context notes, Verification.
+4. Route to the workflow's primary specialist and only add supporting specialists when needed.
+5. If freshness or public comparison matters, run `deep-research` before implementation and use official docs as primary evidence.
+6. Return actions taken, verification evidence, and any gaps.
+
+Workflow source:
+# Migrate Workflow
+
+## When to use
+
+Use this for technology migrations, framework upgrades, dependency updates, or major version transitions.
+
+## Routing
+
+- Primary specialist: `@code-archaeologist`
+- Implementation support: `@backend-specialist`, `@frontend-specialist`
+- Verification support: `@test-engineer`, `@validator`
+
+## Context notes
+
+- This workflow file, active platform rules, and selected agents or skills guide execution.
+- Attach the migration target, current versions, breaking change lists, and impact assessment.
+- Read `ENGINEERING_RULES.md` and `docs/foundation/TECH.md` first because migrations often change accepted patterns and current-state architecture at the same time. After migration, flag updates needed in `docs/foundation/ARCHITECTURE.md` for `## Risks And Tech Debt`.
+
+## Skill Routing
+
+- Primary skills: `legacy-modernizer`, `system-design`
+- Supporting skills (optional): `static-analysis`, `testing-patterns`, `typescript-pro`, `javascript-pro`, `python-pro`, `golang-pro`
+- Start with `legacy-modernizer` for migration methodology and `system-design` for system impact. Add `static-analysis` for automated codemod or compatibility analysis.
+
+## Workflow steps
+
+1. Assess current state and migration target.
+2. Map breaking changes and affected code paths.
+3. Plan incremental migration steps with rollback points.
+4. Execute migration one step at a time with verification.
+5. Update tests and documentation for new patterns.
+6. Set `doc_impact` when the migration changes architecture, deployment shape, boundaries, or design-system rules.
+7. Verify full system behavior after migration complete.
+
+## Verification
+
+- All breaking changes addressed.
+- Tests pass on migrated code.
+- Rollback tested at each migration step.
+- No degradation in performance or functionality.
+- Documentation updated for new patterns.
+
+## Output Contract
+
+```yaml
+MIGRATE_WORKFLOW_RESULT:
+  primary_agent: code-archaeologist
+  supporting_agents: [backend-specialist?, frontend-specialist?, test-engineer?, validator?]
+  primary_skills: [legacy-modernizer, system-design]
+  supporting_skills: [static-analysis?, testing-patterns?]
+  migration:
+    from: <string>
+    to: <string>
+    breaking_changes: [<string>]
+    steps_completed: [<string>]
+    rollback_points: [<string>]
+  verification:
+    tests_passed: true | false
+    performance_impact: <string>
+  doc_impact: none | tech | rules | both
+  follow_up_items: [<string>] | []
+```

package/workflows/workflows/agent-environment-setup/platforms/copilot/prompts/mobile.prompt.md

@@ -0,0 +1,80 @@
+# Workflow Prompt: /mobile
+
+Drive mobile implementation decisions for Flutter/cross-platform behavior and reliability.
+
+Execution contract:
+1. Treat route selection as already resolved by this command; do not begin with skill discovery.
+2. Read `docs/foundation/PRODUCT.md`, `ENGINEERING_RULES.md`, `docs/foundation/ARCHITECTURE.md`, and `docs/foundation/TECH.md` in that order when they exist before non-trivial execution.
+Attached skills:
+- Load these exact skill IDs first: `expo-app`, `react-native`, `stitch`, `frontend-design`, `swift-best-practices`, `kotlin-best-practices`.
+- Local skill file hints if installed: `.github/skills/expo-app/SKILL.md`, `.github/skills/react-native/SKILL.md`, `.github/skills/stitch/SKILL.md`, `.github/skills/frontend-design/SKILL.md`, `.github/skills/swift-best-practices/SKILL.md`, `.github/skills/kotlin-best-practices/SKILL.md`.
+- Treat the skill bundle as already resolved for this workflow. Do not start with route discovery.
+3. Apply workflow sections in order: When to use, Workflow steps, Context notes, Verification.
+4. Route to the workflow's primary specialist and only add supporting specialists when needed.
+5. If freshness or public comparison matters, run `deep-research` before implementation and use official docs as primary evidence.
+6. Return actions taken, verification evidence, and any gaps.
+
+Workflow source:
+# Mobile Workflow
+
+## When to use
+
+Use this for mobile app development, Flutter architecture, Stitch-driven mobile screen handoff, native integrations, or platform-specific behavior.
+
+## Routing
+
+- Primary specialist: `@mobile-developer`
+- Design support: `@frontend-specialist`
+- Verification support: `@test-engineer`
+
+## Context notes
+
+- This workflow file, active platform rules, and selected agents or skills guide execution.
+- Attach platform targets (iOS, Android, both), Flutter version, and relevant screen/feature context.
+- Read `ENGINEERING_RULES.md` and `docs/foundation/TECH.md` before implementing non-trivial mobile work so screens and features follow the declared architecture and design-system rules. Check `docs/foundation/PRODUCT.md` for `## Domain Glossary` to use consistent terminology.
+
+## Skill Routing
+
+- Primary skills: `flutter-feature`, `mobile-design`
+- Supporting skills (optional): `stitch`, `i18n-localization`, `flutter-riverpod`, `flutter-go-router`, `flutter-design-system`, `flutter-testing`, `flutter-drift`, `flutter-offline-sync`, `flutter-state-machine`, `flutter-repository`, `dart-pro`, `swift-pro`, `kotlin-pro`
+- Start with `flutter-feature` for feature implementation and `mobile-design` for UX patterns. Add framework-specific Flutter skill when applicable. Add `i18n-localization` for multi-language support.
+- When the request starts from Stitch artifacts or a design sync, load `stitch` first and then pair it with `mobile-design` plus the narrowest mobile implementation skill for the target stack.
+
+## Workflow steps
+
+1. Clarify platform targets and feature requirements.
+2. Design architecture with platform-appropriate patterns.
+3. Implement with consideration for iOS/Android differences.
+4. Write widget and integration tests.
+5. Review for platform-specific edge cases and UX conventions.
+6. Set `doc_impact` if the feature changes navigation, shared UI rules, or mobile architecture conventions.
+
+## Verification
+
+- Runs correctly on both target platforms.
+- Platform-specific conventions respected (iOS/Android).
+- Touch targets and gesture feedback appropriate.
+- Widget tests cover core behavior.
+- Offline behavior tested if applicable.
+
+## Output Contract
+
+```yaml
+MOBILE_WORKFLOW_RESULT:
+  primary_agent: mobile-developer
+  supporting_agents: [frontend-specialist?, test-engineer?]
+  primary_skills: [flutter-feature, mobile-design]
+  supporting_skills: [stitch?, i18n-localization?, flutter-riverpod?, flutter-testing?, <flutter-specific>?]
+  implementation:
+    platforms: [ios, android]
+    architecture_decisions: [<string>]
+    changed_artifacts: [<path>]
+  testing:
+    widget_tests: [<path>]
+    integration_tests: [<path>] | []
+  platform_notes:
+    ios: [<string>] | []
+    android: [<string>] | []
+  doc_impact: none | tech | rules | both
+  follow_up_items: [<string>] | []
+```

package/workflows/workflows/agent-environment-setup/platforms/copilot/prompts/onboard.prompt.md

@@ -0,0 +1,74 @@
+# Workflow Prompt: /onboard
+
+Survey an unfamiliar codebase, map its architecture, identify patterns and conventions, and produce a structured orientation report for new contributors.
+
+Execution contract:
+1. Treat route selection as already resolved by this command; do not begin with skill discovery.
+2. Read `docs/foundation/PRODUCT.md`, `ENGINEERING_RULES.md`, `docs/foundation/ARCHITECTURE.md`, and `docs/foundation/TECH.md` in that order when they exist before non-trivial execution.
+Attached skills:
+- Load these exact skill IDs first: `deep-research`, `system-design`, `database-design`, `typescript-best-practices`, `javascript-best-practices`, `python-best-practices`.
+- Local skill file hints if installed: `.github/skills/deep-research/SKILL.md`, `.github/skills/system-design/SKILL.md`, `.github/skills/database-design/SKILL.md`, `.github/skills/typescript-best-practices/SKILL.md`, `.github/skills/javascript-best-practices/SKILL.md`, `.github/skills/python-best-practices/SKILL.md`.
+- Treat the skill bundle as already resolved for this workflow. Do not start with route discovery.
+3. Apply workflow sections in order: When to use, Workflow steps, Context notes, Verification.
+4. Route to the workflow's primary specialist and only add supporting specialists when needed.
+5. If freshness or public comparison matters, run `deep-research` before implementation and use official docs as primary evidence.
+6. Return actions taken, verification evidence, and any gaps.
+
+Workflow source:
+# Onboard Workflow
+
+## When to use
+
+Use this when joining a new project, exploring an unfamiliar codebase, or preparing orientation material.
+
+## Routing
+
+- Primary specialist: `@researcher`
+- Architecture mapping: `@code-archaeologist`
+- Domain specialists as needed: `@backend-specialist`, `@frontend-specialist`
+
+## Context notes
+
+- This workflow file, active platform rules, and selected agents or skills guide execution.
+- Provide the repo URL, focus areas, and any specific questions to answer during onboarding.
+- Read `ENGINEERING_RULES.md` first, then `docs/foundation/TECH.md`, `docs/foundation/PRODUCT.md`, and `docs/foundation/ARCHITECTURE.md` when present so onboarding distinguishes the intended contract from current implementation reality. Use the `## Domain Glossary` in PRODUCT.md to learn project-specific terms, and `## Build And Validation` in TECH.md to set up the local environment.
+
+## Skill Routing
+
+- Primary skills: `deep-research`, `system-design`
+- Supporting skills (optional): `legacy-modernizer`, `database-design`, `typescript-pro`, `javascript-pro`, `python-pro`
+- Start with `deep-research` for systematic exploration and `system-design` for architecture mapping. Add `legacy-modernizer` for undocumented systems. Prefer repo evidence first; use external sources only when setup or dependency behavior cannot be confirmed locally.
+
+## Workflow steps
+
+1. Survey the project structure — directories, entry points, and configuration.
+2. Map the architecture — components, data flow, and integration points.
+3. Identify patterns — naming conventions, design patterns, and coding standards.
+4. Document dependencies — external services, databases, and APIs.
+5. Produce orientation report with development setup instructions.
+
+## Verification
+
+- All major components identified and documented.
+- Development setup instructions verified (can be followed by a newcomer).
+- Architecture diagram or description covers main data flows.
+- Key patterns and conventions explicitly documented.
+
+## Output Contract
+
+```yaml
+ONBOARD_WORKFLOW_RESULT:
+  primary_agent: researcher
+  supporting_agents: [code-archaeologist?, backend-specialist?, frontend-specialist?]
+  primary_skills: [deep-research, system-design]
+  supporting_skills: [legacy-modernizer?, database-design?]
+  project_overview:
+    purpose: <string>
+    tech_stack: [<string>]
+    architecture: <string>
+  key_components: [<string>]
+  patterns_and_conventions: [<string>]
+  development_setup: [<step>]
+  dependencies: [<string>]
+  knowledge_gaps: [<string>] | []
+```

package/workflows/workflows/agent-environment-setup/platforms/{antigravity/workflows/orchestrate.md → copilot/prompts/orchestrate.prompt.md}

@@ -1,9 +1,20 @@
----
-command: "/orchestrate"
-description: "Coordinate multiple specialists to solve cross-cutting tasks with explicit ownership, validation gates, and repeat-until-good iteration."
-triggers: ["orchestrate", "coordinate", "multi-area", "cross-team", "handoff"]
----
-
+# Workflow Prompt: /orchestrate
+
+Coordinate multiple specialists to solve cross-cutting tasks with explicit ownership, validation gates, and repeat-until-good iteration.
+
+Execution contract:
+1. Treat route selection as already resolved by this command; do not begin with skill discovery.
+2. Read `docs/foundation/PRODUCT.md`, `ENGINEERING_RULES.md`, `docs/foundation/ARCHITECTURE.md`, and `docs/foundation/TECH.md` in that order when they exist before non-trivial execution.
+Attached skills:
+- Load these exact skill IDs first: `system-design`, `api-design`, `database-design`, `deep-research`, `mcp-server-builder`, `tech-doc`, `prompt-engineering`, `skill-creator`.
+- Local skill file hints if installed: `.github/skills/system-design/SKILL.md`, `.github/skills/api-design/SKILL.md`, `.github/skills/database-design/SKILL.md`, `.github/skills/deep-research/SKILL.md`, `.github/skills/mcp-server-builder/SKILL.md`, `.github/skills/tech-doc/SKILL.md`, `.github/skills/prompt-engineering/SKILL.md`, `.github/skills/skill-creator/SKILL.md`.
+- Treat the skill bundle as already resolved for this workflow. Do not start with route discovery.
+3. Apply workflow sections in order: When to use, Workflow steps, Context notes, Verification.
+4. Route to the workflow's primary specialist and only add supporting specialists when needed.
+5. If freshness or public comparison matters, run `deep-research` before implementation and use official docs as primary evidence.
+6. Return actions taken, verification evidence, and any gaps.
+
+Workflow source:
 # Orchestrate Workflow
 
 ## When to use
@@ -12,9 +23,9 @@ Use this when a task spans multiple domains (backend + frontend, security + infr
 
 ## Routing
 
-- Primary coordinator: `.agent/agents/orchestrator`
-- Specialist routing determined by task decomposition — delegates to `.agent/agents/backend-specialist`, `.agent/agents/frontend-specialist`, `.agent/agents/database-architect`, `.agent/agents/security-auditor`, `.agent/agents/ci-cd-pipeline`, `.agent/agents/test-engineer`, `.agent/agents/mobile-developer`, or other specialist agents as needed.
-- Validation support: `.agent/agents/validator`
+- Primary coordinator: `@orchestrator`
+- Specialist routing determined by task decomposition — delegates to `@backend-specialist`, `@frontend-specialist`, `@database-architect`, `@security-auditor`, `@devops-engineer`, `@test-engineer`, `@mobile-developer`, or other specialist agents as needed.
+- Validation support: `@validator`
 
 ## Context notes
 
@@ -25,7 +36,7 @@ Use this when a task spans multiple domains (backend + frontend, security + infr
 ## Skill Routing
 
 - Primary skills: `system-design`, `api-design`
-- Supporting skills (optional): `database-design`, `deep-research`, `mcp-server-builder`, `tech-doc`, `prompt-engineering`, `skill-creator`
+- Supporting skills (optional): `database-design`, `deep-research`, `mcp-server-builder`, `openai-docs`, `prompt-engineering`, `skill-creator`
 - Start with `system-design` for system design coordination and `api-design` for integration contracts. Add `deep-research` before implementation when the coordination challenge depends on fresh external facts or public comparison.
 
 ## Workflow steps
@@ -69,5 +80,3 @@ ORCHESTRATE_WORKFLOW_RESULT:
   remaining_risks: [<string>] | []
   follow_up_actions: [<string>] | []
 ```
-
-> **Antigravity note:** Use Agent Manager for parallel agent coordination. Workflow files are stored under `.agent/workflows/`.

package/workflows/workflows/agent-environment-setup/platforms/{antigravity/workflows/plan.md → copilot/prompts/plan.prompt.md}

@@ -1,20 +1,20 @@
----
-command: "/plan"
-description: "Build a decision-complete implementation plan with interfaces, failure modes, and acceptance criteria."
-triggers:
-  [
-    "plan",
-    "design",
-    "roadmap",
-    "acceptance",
-    "brainstorm",
-    "idea",
-    "options",
-    "tradeoff",
-    "approach",
-  ]
----
-
+# Workflow Prompt: /plan
+
+Build a decision-complete implementation plan with interfaces, failure modes, and acceptance criteria.
+
+Execution contract:
+1. Treat route selection as already resolved by this command; do not begin with skill discovery.
+2. Read `docs/foundation/PRODUCT.md`, `ENGINEERING_RULES.md`, `docs/foundation/ARCHITECTURE.md`, and `docs/foundation/TECH.md` in that order when they exist before non-trivial execution.
+Attached skills:
+- Load these exact skill IDs first: `system-design`, `api-design`, `database-design`, `deep-research`, `mcp-server-builder`, `tech-doc`, `prompt-engineering`, `skill-creator`.
+- Local skill file hints if installed: `.github/skills/system-design/SKILL.md`, `.github/skills/api-design/SKILL.md`, `.github/skills/database-design/SKILL.md`, `.github/skills/deep-research/SKILL.md`, `.github/skills/mcp-server-builder/SKILL.md`, `.github/skills/tech-doc/SKILL.md`, `.github/skills/prompt-engineering/SKILL.md`, `.github/skills/skill-creator/SKILL.md`.
+- Treat the skill bundle as already resolved for this workflow. Do not start with route discovery.
+3. Apply workflow sections in order: When to use, Workflow steps, Context notes, Verification.
+4. Route to the workflow's primary specialist and only add supporting specialists when needed.
+5. If freshness or public comparison matters, run `deep-research` before implementation and use official docs as primary evidence.
+6. Return actions taken, verification evidence, and any gaps.
+
+Workflow source:
 # Plan Workflow
 
 ## When to use
@@ -23,9 +23,9 @@ Use this when starting a new feature, project, or significant change that needs
 
 ## Routing
 
-- Primary coordinator: `.agent/agents/project-planner`
-- Architecture support: `.agent/agents/orchestrator`
-- Domain validation: `.agent/agents/backend-specialist`, `.agent/agents/frontend-specialist`, `.agent/agents/database-architect`
+- Primary coordinator: `@project-planner`
+- Architecture support: `@orchestrator`
+- Domain validation: `@backend-specialist`, `@frontend-specialist`, `@database-architect`
 
 ## Context notes
 
@@ -37,7 +37,7 @@ Use this when starting a new feature, project, or significant change that needs
 ## Skill Routing
 
 - Primary skills: `system-design`, `api-design`
-- Supporting skills (optional): `database-design`, `deep-research`, `mcp-server-builder`, `tech-doc`, `prompt-engineering`, `skill-creator`
+- Supporting skills (optional): `database-design`, `deep-research`, `mcp-server-builder`, `openai-docs`, `prompt-engineering`, `skill-creator`
 - Start with `system-design` for system design and `api-design` for API contracts. Add `database-design` when data modeling is central, `deep-research` when fresh external knowledge or public comparison is needed.
 
 ## Workflow steps
@@ -86,5 +86,3 @@ PLAN_WORKFLOW_RESULT:
   traceability_status: complete | partial | blocked
   follow_up_items: [<string>] | []
 ```
-
-> **Antigravity note:** Use Agent Manager for parallel agent coordination. Workflow files are stored under `.agent/workflows/`.

package/workflows/workflows/agent-environment-setup/platforms/copilot/prompts/refactor.prompt.md

@@ -0,0 +1,76 @@
+# Workflow Prompt: /refactor
+
+Improve maintainability while preserving behavior through incremental safe refactoring.
+
+Execution contract:
+1. Treat route selection as already resolved by this command; do not begin with skill discovery.
+2. Read `docs/foundation/PRODUCT.md`, `ENGINEERING_RULES.md`, `docs/foundation/ARCHITECTURE.md`, and `docs/foundation/TECH.md` in that order when they exist before non-trivial execution.
+Attached skills:
+- Load these exact skill IDs first: `code-review`, `system-design`, `unit-testing`, `typescript-best-practices`, `javascript-best-practices`, `python-best-practices`, `golang-best-practices`.
+- Local skill file hints if installed: `.github/skills/code-review/SKILL.md`, `.github/skills/system-design/SKILL.md`, `.github/skills/unit-testing/SKILL.md`, `.github/skills/typescript-best-practices/SKILL.md`, `.github/skills/javascript-best-practices/SKILL.md`, `.github/skills/python-best-practices/SKILL.md`, `.github/skills/golang-best-practices/SKILL.md`.
+- Treat the skill bundle as already resolved for this workflow. Do not start with route discovery.
+3. Apply workflow sections in order: When to use, Workflow steps, Context notes, Verification.
+4. Route to the workflow's primary specialist and only add supporting specialists when needed.
+5. If freshness or public comparison matters, run `deep-research` before implementation and use official docs as primary evidence.
+6. Return actions taken, verification evidence, and any gaps.
+
+Workflow source:
+# Refactor Workflow
+
+## When to use
+
+Use this when improving code structure, reducing tech debt, or modularizing without changing behavior.
+
+## Routing
+
+- Primary specialist: `@code-archaeologist`
+- Domain support: `@backend-specialist`, `@frontend-specialist`
+- Verification support: `@test-engineer`, `@validator`
+
+## Context notes
+
+- This workflow file, active platform rules, and selected agents or skills guide execution.
+- Attach the target code, pain points, and any constraints on what can change.
+- Read `ENGINEERING_RULES.md` and `docs/foundation/TECH.md` first so behavior-preserving structure changes do not drift from the accepted architecture contract. Check `docs/foundation/ARCHITECTURE.md` for `## Dependency Rules` and `## Crosscutting Concerns` before restructuring.
+
+## Skill Routing
+
+- Primary skills: `static-analysis`, `legacy-modernizer`
+- Supporting skills (optional): `testing-patterns`, `system-design`, `typescript-pro`, `javascript-pro`, `python-pro`, `golang-pro`
+- Start with `static-analysis` for automated code quality assessment. Add `legacy-modernizer` for modernization patterns. Add `testing-patterns` when refactoring needs test coverage to proceed safely.
+
+## Workflow steps
+
+1. Map the current structure and identify refactoring targets.
+2. Ensure adequate test coverage before modifying (add tests if needed).
+3. Apply one refactoring at a time with behavior preservation.
+4. Verify behavior unchanged after each step.
+5. Document the improved structure and any conventions established.
+6. Set `doc_impact` when the refactor changes project structure, module boundaries, or design-system conventions.
+
+## Verification
+
+- All existing tests pass after each refactoring step.
+- No behavioral changes introduced (unless explicitly intended).
+- Code quality metrics improved (complexity, coupling, cohesion).
+- New tests added for any gaps discovered during refactoring.
+
+## Output Contract
+
+```yaml
+REFACTOR_WORKFLOW_RESULT:
+  primary_agent: code-archaeologist
+  supporting_agents: [backend-specialist?, frontend-specialist?, test-engineer?, validator?]
+  primary_skills: [static-analysis, legacy-modernizer]
+  supporting_skills: [testing-patterns?, system-design?]
+  refactoring_summary:
+    targets: [<string>]
+    changes_applied: [<string>]
+    behavior_preserved: true | false
+  quality_improvement:
+    complexity_before: <string>
+    complexity_after: <string>
+  doc_impact: none | tech | rules | both
+  tests_added: [<test-file-path>] | []
+  follow_up_items: [<string>] | []
+```

package/workflows/workflows/agent-environment-setup/platforms/copilot/prompts/release.prompt.md

@@ -0,0 +1,79 @@
+# Workflow Prompt: /release
+
+Prepare and execute release with rollout guardrails, verification, and rollback plan.
+
+Execution contract:
+1. Treat route selection as already resolved by this command; do not begin with skill discovery.
+2. Read `docs/foundation/PRODUCT.md`, `ENGINEERING_RULES.md`, `docs/foundation/ARCHITECTURE.md`, and `docs/foundation/TECH.md` in that order when they exist before non-trivial execution.
+Attached skills:
+- Load these exact skill IDs first: `ci-cd-pipeline`, `git-workflow`, `tech-doc`, `observability`, `kubernetes-deploy`, `typescript-best-practices`, `javascript-best-practices`.
+- Local skill file hints if installed: `.github/skills/ci-cd-pipeline/SKILL.md`, `.github/skills/git-workflow/SKILL.md`, `.github/skills/tech-doc/SKILL.md`, `.github/skills/observability/SKILL.md`, `.github/skills/kubernetes-deploy/SKILL.md`, `.github/skills/typescript-best-practices/SKILL.md`, `.github/skills/javascript-best-practices/SKILL.md`.
+- Treat the skill bundle as already resolved for this workflow. Do not start with route discovery.
+3. Apply workflow sections in order: When to use, Workflow steps, Context notes, Verification.
+4. Route to the workflow's primary specialist and only add supporting specialists when needed.
+5. If freshness or public comparison matters, run `deep-research` before implementation and use official docs as primary evidence.
+6. Return actions taken, verification evidence, and any gaps.
+
+Workflow source:
+# Release Workflow
+
+## When to use
+
+Use this when preparing a release, deploying to production, or managing a rollout.
+
+## Routing
+
+- Primary coordinator: `@devops-engineer`
+- Release verification: `@test-engineer`, `@validator`
+- Documentation: `@documentation-writer`
+
+## Context notes
+
+- This workflow file, active platform rules, and selected agents or skills guide execution.
+- Attach the release scope, version number, changelog draft, and deployment target.
+- Read `ENGINEERING_RULES.md` and `docs/foundation/TECH.md` before release if the shipped changes touched architecture, scaling assumptions, or design-system rules. Check `docs/foundation/TECH.md` for `## Build And Validation` and `## CI CD Pipeline` steps to verify the release pipeline.
+
+## Skill Routing
+
+- Primary skills: `ci-cd-pipelines`, `git-workflow`
+- Supporting skills (optional): `changelog-generator`, `devops-engineer`, `sre-engineer`, `docker-kubernetes`, `observability`, `serverless-patterns`, `typescript-pro`, `javascript-pro`
+- Start with `ci-cd-pipelines` for deployment automation and `git-workflow` for release branching. Add `changelog-generator` for release notes.
+
+## Workflow steps
+
+1. Finalize scope — confirm all changes are merged and tested.
+2. Generate changelog and release notes.
+3. Prepare deployment artifacts and configuration.
+4. Execute staged rollout with health checks at each stage.
+5. Verify production health post-deployment.
+6. Document rollback procedure and post-release status.
+7. Set `doc_impact` if the release includes architecture-affecting work that should refresh the managed docs.
+
+## Verification
+
+- All tests pass on release branch/tag.
+- Changelog accurately reflects changes.
+- Deployment artifacts built and verified.
+- Production health confirmed after rollout.
+- Rollback procedure tested or documented.
+
+## Output Contract
+
+```yaml
+RELEASE_WORKFLOW_RESULT:
+  primary_agent: devops-engineer
+  supporting_agents: [test-engineer?, validator?, documentation-writer?]
+  primary_skills: [ci-cd-pipelines, git-workflow]
+  supporting_skills: [changelog-generator?, devops-engineer?, sre-engineer?]
+  release:
+    version: <string>
+    changelog: <string>
+    artifacts: [<string>]
+  deployment:
+    strategy: <staged | canary | blue-green | direct>
+    stages_completed: [<string>]
+    health_checks: [<string>]
+  rollback_plan: <string>
+  doc_impact: none | tech | rules | both
+  follow_up_items: [<string>] | []
+```

package/workflows/workflows/agent-environment-setup/platforms/copilot/prompts/review.prompt.md

@@ -0,0 +1,75 @@
+# Workflow Prompt: /review
+
+Run a strict review for bugs, regressions, accessibility issues, security risk, and code quality with prioritized findings.
+
+Execution contract:
+1. Treat route selection as already resolved by this command; do not begin with skill discovery.
+2. Read `docs/foundation/PRODUCT.md`, `ENGINEERING_RULES.md`, `docs/foundation/ARCHITECTURE.md`, and `docs/foundation/TECH.md` in that order when they exist before non-trivial execution.
+Attached skills:
+- Load these exact skill IDs first: `code-review`, `unit-testing`, `owasp-security-review`, `performance-testing`, `react`, `nextjs`, `typescript-best-practices`, `javascript-best-practices`, `python-best-practices`, `golang-best-practices`.
+- Local skill file hints if installed: `.github/skills/code-review/SKILL.md`, `.github/skills/unit-testing/SKILL.md`, `.github/skills/owasp-security-review/SKILL.md`, `.github/skills/performance-testing/SKILL.md`, `.github/skills/react/SKILL.md`, `.github/skills/nextjs/SKILL.md`, `.github/skills/typescript-best-practices/SKILL.md`, `.github/skills/javascript-best-practices/SKILL.md`.
+- Treat the skill bundle as already resolved for this workflow. Do not start with route discovery.
+3. Apply workflow sections in order: When to use, Workflow steps, Context notes, Verification.
+4. Route to the workflow's primary specialist and only add supporting specialists when needed.
+5. If freshness or public comparison matters, run `deep-research` before implementation and use official docs as primary evidence.
+6. Return actions taken, verification evidence, and any gaps.
+
+Workflow source:
+# Review Workflow
+
+## When to use
+
+Use this for code review, PR review, or quality audit of existing code changes.
+
+## Routing
+
+- Primary specialist: `@frontend-specialist` (for frontend code) or `@backend-specialist` (for backend code)
+- Security review: `@security-auditor`
+- Quality validation: `@validator`
+- Verification support: `@test-engineer`
+
+## Context notes
+
+- This workflow file, active platform rules, and selected agents or skills guide execution.
+- Attach the PR diff, changed files, or specific code paths to review.
+
+## Skill Routing
+
+- Primary skills: `frontend-code-review`, `static-analysis`, `testing-patterns`
+- Supporting skills (optional): `security-engineer`, `vulnerability-scanner`, `web-perf`, `react-expert`, `nextjs-developer`, `typescript-pro`, `javascript-pro`, `python-pro`, `golang-pro`
+- Start with `frontend-code-review` for UI code or `static-analysis` for backend code. Add `testing-patterns` when evaluating test quality. Add `security-engineer` for security-sensitive changes.
+
+## Workflow steps
+
+1. Understand the intent and scope of the changes.
+2. Review for correctness — logic bugs, edge cases, and regressions.
+3. Review for security — input validation, auth, secrets exposure.
+4. Review for accessibility — WCAG compliance, keyboard navigation, screen readers.
+5. Review for performance — unnecessary re-renders, N+1 queries, bundle impact.
+6. Prioritize findings by severity and provide actionable feedback.
+
+## Verification
+
+- Each finding has severity, location, and suggested fix.
+- Findings prioritized: critical > high > medium > low.
+- Positive observations noted alongside issues.
+- Reviewed against codebase conventions.
+
+## Output Contract
+
+```yaml
+REVIEW_WORKFLOW_RESULT:
+  primary_agent: <frontend-specialist | backend-specialist>
+  supporting_agents: [security-auditor?, validator?, test-engineer?]
+  primary_skills: [frontend-code-review?, static-analysis?, testing-patterns?]
+  supporting_skills: [security-engineer?, vulnerability-scanner?, web-perf?]
+  findings:
+    - severity: critical | high | medium | low
+      category: correctness | security | accessibility | performance | style
+      location: <file:line>
+      description: <string>
+      suggestion: <string>
+  overall_assessment: approve | request_changes | reject
+  positive_observations: [<string>] | []
+  follow_up_items: [<string>] | []
+```