@cubis/foundry 0.3.82 → 0.3.83

package/workflows/workflows/agent-environment-setup/platforms/gemini/commands/backend.toml

@@ -1,19 +1,86 @@
 description = "Drive backend architecture, API operations, and Postman-oriented execution with API, data, and reliability focus."
 prompt = '''
-Follow the /backend workflow from .gemini/workflows/backend.md.
+Execute the native projection of the /backend workflow.
+
+Drive backend architecture, API operations, and Postman-oriented execution with API, data, and reliability focus.
 
 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: `api-design`, `javascript-best-practices`, `owasp-security-review`, `database-design`, `nestjs`, `fastapi`, `microservices-design`, `drizzle-orm`, `stripe-integration`, `ci-cd-pipeline`, `frontend-design`, `typescript-best-practices`, `python-best-practices`, `golang-best-practices`.
-- Local skill file hints if installed: `.gemini/skills/api-design/SKILL.md`, `.gemini/skills/javascript-best-practices/SKILL.md`, `.gemini/skills/owasp-security-review/SKILL.md`, `.gemini/skills/database-design/SKILL.md`, `.gemini/skills/nestjs/SKILL.md`, `.gemini/skills/fastapi/SKILL.md`, `.gemini/skills/microservices-design/SKILL.md`, `.gemini/skills/drizzle-orm/SKILL.md`.
+- Local skill file hints if installed: `.agents/skills/api-design/SKILL.md`, `.agents/skills/javascript-best-practices/SKILL.md`, `.agents/skills/owasp-security-review/SKILL.md`, `.agents/skills/database-design/SKILL.md`, `.agents/skills/nestjs/SKILL.md`, `.agents/skills/fastapi/SKILL.md`, `.agents/skills/microservices-design/SKILL.md`, `.agents/skills/drizzle-orm/SKILL.md`.
 - Treat the skill bundle as already resolved for this workflow. Do not start with route discovery.
-3. Confirm the request fits the workflow's "When to use" section.
+3. Confirm the request fits the workflow's "When to use" section before acting.
 4. Execute according to "Workflow steps" and apply "Context notes".
 5. Complete "Verification" checks and report concrete evidence.
-6. If freshness, public comparison, or explicit research needs appear, pause implementation and load `deep-research` or route to the researcher posture first.
+6. If freshness, public comparison, or explicit research needs appear, pause implementation and load `deep-research` or route to research first.
 7. For outside evidence: repo first, official docs next, Reddit/community only as labeled secondary evidence.
 
+Workflow source:
+# Backend Workflow
+
+## When to use
+
+Use this for backend architecture, API design, service implementation, or Postman-oriented API operations.
+
+## Routing
+
+- Primary specialist: `@backend-specialist`
+- Database support: `@database-architect`
+- Security review: `@security-auditor`
+- Verification support: `@test-engineer`
+
+## Context notes
+
+- This workflow file, active platform rules, and selected agents or skills guide execution.
+- Attach API specifications, schema diagrams, Postman collections, and relevant service code.
+- Read `ENGINEERING_RULES.md` and `TECH.md` before changing service boundaries or shared backend structure.
+
+## Skill Routing
+
+- Primary skills: `api-design`, `api-patterns`, `nodejs-best-practices`
+- Supporting skills (optional): `auth-architect`, `database-design`, `database-design`, `nestjs-expert`, `fastapi-expert`, `graphql-architect`, `microservices-architect`, `drizzle-expert`, `firebase`, `stripe-best-practices`, `serverless-patterns`, `i18n-localization`, `typescript-pro`, `javascript-pro`, `python-pro`, `golang-pro`
+- Start with `api-design` for API contract work and `nodejs-best-practices` for Node.js services. Add framework-specific skill when applicable.
+
+## Workflow steps
+
+1. Clarify API contracts and data model requirements.
+2. Design or review schema and service boundaries.
+3. Implement backend logic with proper error handling and validation.
+4. Write integration tests covering happy path and error cases.
+5. Review for security, performance, and reliability.
+6. Set `doc_impact` if the change alters service boundaries, shared contracts, or operational shape.
+
+## Verification
+
+- API contracts match specification.
+- All endpoints have input validation and error handling.
+- Integration tests cover happy path and key error cases.
+- No N+1 queries or unindexed access patterns.
+- Auth applied correctly to protected endpoints.
+
+## Output Contract
+
+```yaml
+BACKEND_WORKFLOW_RESULT:
+  primary_agent: backend-specialist
+  supporting_agents: [database-architect?, security-auditor?, test-engineer?]
+  primary_skills: [api-design, api-patterns, nodejs-best-practices]
+  supporting_skills: [auth-architect?, database-design?, <framework-skill>?]
+  api_changes:
+    endpoints_created: [<string>] | []
+    endpoints_modified: [<string>] | []
+    schema_changes: [<string>] | []
+  implementation:
+    files_changed: [<path>]
+    tests_added: [<path>]
+  doc_impact: none | tech | rules | both
+  verification:
+    checks_run: [<command-or-test>]
+    evidence: [<string>]
+  follow_up_items: [<string>] | []
+```
+
 If command arguments are provided, treat them as additional user context.
 '''

package/workflows/workflows/agent-environment-setup/platforms/gemini/commands/create.toml

@@ -1,19 +1,83 @@
 description = "Implement feature work with minimal blast radius and clear verification checkpoints."
 prompt = '''
-Follow the /create workflow from .gemini/workflows/create.md.
+Execute the native projection of the /create workflow.
+
+Implement feature work with minimal blast radius and clear verification checkpoints.
 
 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: `typescript-best-practices`, `javascript-best-practices`, `python-best-practices`, `golang-best-practices`, `java-best-practices`, `csharp-best-practices`, `kotlin-best-practices`, `rust-best-practices`, `php-best-practices`, `expo-app`, `swift-best-practices`, `api-design`, `nestjs`, `fastapi`, `drizzle-orm`, `database-design`, `mcp-server-builder`, `stitch`, `react`, `nextjs`, `frontend-design`, `performance-testing`, `skill-creator`, `stripe-integration`, `ci-cd-pipeline`.
-- Local skill file hints if installed: `.gemini/skills/typescript-best-practices/SKILL.md`, `.gemini/skills/javascript-best-practices/SKILL.md`, `.gemini/skills/python-best-practices/SKILL.md`, `.gemini/skills/golang-best-practices/SKILL.md`, `.gemini/skills/java-best-practices/SKILL.md`, `.gemini/skills/csharp-best-practices/SKILL.md`, `.gemini/skills/kotlin-best-practices/SKILL.md`, `.gemini/skills/rust-best-practices/SKILL.md`.
+- Local skill file hints if installed: `.agents/skills/typescript-best-practices/SKILL.md`, `.agents/skills/javascript-best-practices/SKILL.md`, `.agents/skills/python-best-practices/SKILL.md`, `.agents/skills/golang-best-practices/SKILL.md`, `.agents/skills/java-best-practices/SKILL.md`, `.agents/skills/csharp-best-practices/SKILL.md`, `.agents/skills/kotlin-best-practices/SKILL.md`, `.agents/skills/rust-best-practices/SKILL.md`.
 - Treat the skill bundle as already resolved for this workflow. Do not start with route discovery.
-3. Confirm the request fits the workflow's "When to use" section.
+3. Confirm the request fits the workflow's "When to use" section before acting.
 4. Execute according to "Workflow steps" and apply "Context notes".
 5. Complete "Verification" checks and report concrete evidence.
-6. If freshness, public comparison, or explicit research needs appear, pause implementation and load `deep-research` or route to the researcher posture first.
+6. If freshness, public comparison, or explicit research needs appear, pause implementation and load `deep-research` or route to research first.
 7. For outside evidence: repo first, official docs next, Reddit/community only as labeled secondary evidence.
 
+Workflow source:
+# Create Workflow
+
+## 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 or skills guide execution.
+- Attach logs, screenshots, failing output, and relevant paths when context is incomplete.
+- Read `ENGINEERING_RULES.md` first and `TECH.md` next for non-trivial work so new code follows the declared architecture and design-system rules.
+
+## Skill Routing
+
+- Primary skills: `typescript-pro`, `javascript-pro`, `python-pro`, `golang-pro`, `java-pro`, `csharp-pro`, `kotlin-pro`, `rust-pro`, `php-pro`, `ruby-pro`, `c-pro`, `cpp-pro`, `dart-pro`, `swift-pro`
+- Supporting skills (optional): `api-design`, `api-patterns`, `nodejs-best-practices`, `nestjs-expert`, `fastapi-expert`, `graphql-architect`, `drizzle-expert`, `firebase`, `mcp-server-builder`, `stitch`, `react-expert`, `react-best-practices`, `nextjs-developer`, `tailwind-patterns`, `frontend-design`, `design-system-builder`, `web-perf`, `skill-creator`, `stripe-best-practices`, `serverless-patterns`, `i18n-localization`
+- Pick one primary language skill from repo signals or touched files. Add the narrowest specialist only when the feature is clearly backend or frontend framework-specific.
+- If the request references Stitch screens, artifacts, design-to-code, or UI sync, add `stitch` first and route the implementation through the frontend or mobile specialist based on the destination surface.
+
+## Workflow steps
+
+1. Confirm target files and contracts.
+2. Implement smallest coherent increment.
+3. Validate behavior with focused tests.
+4. Capture `doc_impact` when the feature changes architecture, boundaries, scale, or design-system rules.
+5. Capture remaining gaps and follow-ups.
+
+## Verification
+
+- Run focused checks/tests for the changed scope.
+- Confirm no regressions in adjacent behavior.
+- Note any gaps that were not validated.
+
+## Output Contract
+
+```yaml
+CREATE_WORKFLOW_RESULT:
+  primary_agent: orchestrator
+  supporting_agents: [backend-specialist?, frontend-specialist?, mobile-developer?, test-engineer?]
+  primary_skills: [<dominant-language-skill>]
+  supporting_skills: [stitch?, <framework-specific-skills-used>]
+  implemented_scope:
+    summary: <string>
+    changed_artifacts: [<path-or-artifact>]
+  behavioral_impact: [<string>]
+  doc_impact: none | tech | rules | both
+  verification:
+    checks_run: [<command-or-test>]
+    evidence: [<string>]
+    gaps: [<string>] | []
+  follow_up_items: [<string>] | []
+```
+
 If command arguments are provided, treat them as additional user context.
 '''

package/workflows/workflows/agent-environment-setup/platforms/gemini/commands/database.toml

@@ -1,19 +1,82 @@
 description = "Design or review schema, queries, and migrations with performance and integrity controls."
 prompt = '''
-Follow the /database workflow from .gemini/workflows/database.md.
+Execute the native projection of the /database workflow.
+
+Design or review schema, queries, and migrations with performance and integrity controls.
 
 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: `database-design`, `drizzle-orm`, `typescript-best-practices`, `javascript-best-practices`, `python-best-practices`.
-- Local skill file hints if installed: `.gemini/skills/database-design/SKILL.md`, `.gemini/skills/drizzle-orm/SKILL.md`, `.gemini/skills/typescript-best-practices/SKILL.md`, `.gemini/skills/javascript-best-practices/SKILL.md`, `.gemini/skills/python-best-practices/SKILL.md`.
+- Local skill file hints if installed: `.agents/skills/database-design/SKILL.md`, `.agents/skills/drizzle-orm/SKILL.md`, `.agents/skills/typescript-best-practices/SKILL.md`, `.agents/skills/javascript-best-practices/SKILL.md`, `.agents/skills/python-best-practices/SKILL.md`.
 - Treat the skill bundle as already resolved for this workflow. Do not start with route discovery.
-3. Confirm the request fits the workflow's "When to use" section.
+3. Confirm the request fits the workflow's "When to use" section before acting.
 4. Execute according to "Workflow steps" and apply "Context notes".
 5. Complete "Verification" checks and report concrete evidence.
-6. If freshness, public comparison, or explicit research needs appear, pause implementation and load `deep-research` or route to the researcher posture first.
+6. If freshness, public comparison, or explicit research needs appear, pause implementation and load `deep-research` or route to research first.
 7. For outside evidence: repo first, official docs next, Reddit/community only as labeled secondary evidence.
 
+Workflow source:
+# Database Workflow
+
+## When to use
+
+Use this for schema design, query optimization, migration planning, or database architecture decisions.
+
+## Routing
+
+- Primary specialist: `@database-architect`
+- Implementation support: `@backend-specialist`
+- Verification support: `@test-engineer`
+
+## Context notes
+
+- This workflow file, active platform rules, and selected agents or skills guide execution.
+- Attach existing schema, migration history, query patterns, and performance requirements.
+- Read `ENGINEERING_RULES.md` and `TECH.md` before changing data ownership, persistence boundaries, or shared schema conventions.
+
+## Skill Routing
+
+- Primary skills: `database-design`, `database-optimizer`, `database-design`
+- Supporting skills (optional): `drizzle-expert`, `postgres`, `mysql`, `sqlite`, `mongodb`, `redis`, `supabase`, `firebase`, `vitess`, `typescript-pro`, `javascript-pro`, `python-pro`
+- Start with `database-design` for schema work, `database-optimizer` for performance, or `database-design` for general database operations. Add engine-specific skill when applicable.
+
+## Workflow steps
+
+1. Understand current schema and data model.
+2. Design or review proposed changes with normalization analysis.
+3. Plan migration with rollback strategy.
+4. Optimize queries and indexes for known access patterns.
+5. Validate data integrity constraints.
+6. Set `doc_impact` if the change alters data boundaries, core entities, or persistence patterns that future work should follow.
+
+## Verification
+
+- Schema changes maintain referential integrity.
+- Migrations are reversible or have documented rollback plan.
+- EXPLAIN output reviewed for performance-sensitive queries.
+- No breaking changes to existing consumers without migration plan.
+
+## Output Contract
+
+```yaml
+DATABASE_WORKFLOW_RESULT:
+  primary_agent: database-architect
+  supporting_agents: [backend-specialist?, test-engineer?]
+  primary_skills: [database-design, database-optimizer, database-design]
+  supporting_skills: [<engine-specific-skill>?, drizzle-expert?]
+  schema_changes:
+    tables_affected: [<string>]
+    migration_plan: <string>
+    rollback_plan: <string>
+  query_optimization:
+    queries_reviewed: <number>
+    indexes_recommended: [<string>] | []
+  doc_impact: none | tech | rules | both
+  integrity_checks: [<string>]
+  follow_up_items: [<string>] | []
+```
+
 If command arguments are provided, treat them as additional user context.
 '''

package/workflows/workflows/agent-environment-setup/platforms/gemini/commands/debug.toml

@@ -1,19 +1,78 @@
 description = "Isolate root cause quickly, apply the smallest safe remediation, and leave behind regression evidence."
 prompt = '''
-Follow the /debug workflow from .gemini/workflows/debug.md.
+Execute the native projection of the /debug workflow.
+
+Isolate root cause quickly, apply the smallest safe remediation, and leave behind regression evidence.
 
 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: `systematic-debugging`, `observability`, `unit-testing`, `typescript-best-practices`, `javascript-best-practices`, `python-best-practices`, `golang-best-practices`, `java-best-practices`, `csharp-best-practices`, `kotlin-best-practices`, `rust-best-practices`, `integration-testing`, `playwright-interactive`, `skill-creator`.
-- Local skill file hints if installed: `.gemini/skills/systematic-debugging/SKILL.md`, `.gemini/skills/observability/SKILL.md`, `.gemini/skills/unit-testing/SKILL.md`, `.gemini/skills/typescript-best-practices/SKILL.md`, `.gemini/skills/javascript-best-practices/SKILL.md`, `.gemini/skills/python-best-practices/SKILL.md`, `.gemini/skills/golang-best-practices/SKILL.md`, `.gemini/skills/java-best-practices/SKILL.md`.
+- Local skill file hints if installed: `.agents/skills/systematic-debugging/SKILL.md`, `.agents/skills/observability/SKILL.md`, `.agents/skills/unit-testing/SKILL.md`, `.agents/skills/typescript-best-practices/SKILL.md`, `.agents/skills/javascript-best-practices/SKILL.md`, `.agents/skills/python-best-practices/SKILL.md`, `.agents/skills/golang-best-practices/SKILL.md`, `.agents/skills/java-best-practices/SKILL.md`.
 - Treat the skill bundle as already resolved for this workflow. Do not start with route discovery.
-3. Confirm the request fits the workflow's "When to use" section.
+3. Confirm the request fits the workflow's "When to use" section before acting.
 4. Execute according to "Workflow steps" and apply "Context notes".
 5. Complete "Verification" checks and report concrete evidence.
-6. If freshness, public comparison, or explicit research needs appear, pause implementation and load `deep-research` or route to the researcher posture first.
+6. If freshness, public comparison, or explicit research needs appear, pause implementation and load `deep-research` or route to research first.
 7. For outside evidence: repo first, official docs next, Reddit/community only as labeled secondary evidence.
 
+Workflow source:
+# Debug Workflow
+
+## When to use
+
+Use this when behavior is failing, inconsistent, flaky, or only reproducible under certain conditions.
+
+## Routing
+
+- Primary specialist: `@debugger`
+- Domain implementation support: `@backend-specialist`, `@frontend-specialist`
+- Verification support: `@test-engineer`
+
+## Context notes
+
+- This workflow file, active platform rules, and selected agents or skills guide execution.
+- Attach stack traces, request IDs, traces, repro steps, recent diffs, and environment notes when context is incomplete.
+
+## Skill Routing
+
+- Primary skills: `debugging-strategies`, `error-ux-observability`
+- Supporting skills (optional): `testing-patterns`, `typescript-pro`, `javascript-pro`, `python-pro`, `golang-pro`, `java-pro`, `csharp-pro`, `kotlin-pro`, `rust-pro`, `webapp-testing`, `playwright-e2e`, `skill-creator`
+- Start with `debugging-strategies` for reproduce, isolate, instrument, and verify flow. Add `error-ux-observability` when the failure involves error states, logging, or tracing gaps. Add the dominant language skill for exact code-path analysis, `webapp-testing` or `playwright-e2e` when the failure lives in browser or release verification.
+
+## Workflow steps
+
+1. Reproduce the issue and record expected versus actual behavior.
+2. Narrow the fault domain with the smallest useful evidence.
+3. Fix the confirmed cause with the lowest regression risk.
+4. Add or update the regression proof.
+5. Document any remaining uncertainty or environment-specific gaps.
+
+## Verification
+
+- Re-run the failing scenario first.
+- Run focused regression checks on adjacent high-risk paths.
+- Call out any remaining gaps if the full environment could not be reproduced.
+
+## Output Contract
+
+```yaml
+DEBUG_WORKFLOW_RESULT:
+  primary_agent: debugger
+  supporting_agents: [backend-specialist?, frontend-specialist?, test-engineer?]
+  primary_skills: [debugging-strategies, error-ux-observability]
+  supporting_skills: [testing-patterns?, <language-skill>?, webapp-testing?, playwright-e2e?]
+  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>] | []
+```
+
 If command arguments are provided, treat them as additional user context.
 '''

package/workflows/workflows/agent-environment-setup/platforms/gemini/commands/devops.toml

@@ -1,19 +1,79 @@
 description = "Plan and execute deployment, CI/CD, incident response, and operational safety changes with rollback controls."
 prompt = '''
-Follow the /devops workflow from .gemini/workflows/devops.md.
+Execute the native projection of the /devops workflow.
+
+Plan and execute deployment, CI/CD, incident response, and operational safety changes with rollback controls.
 
 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`, `kubernetes-deploy`, `observability`, `git-workflow`, `systematic-debugging`, `typescript-best-practices`, `javascript-best-practices`, `python-best-practices`, `golang-best-practices`.
-- Local skill file hints if installed: `.gemini/skills/ci-cd-pipeline/SKILL.md`, `.gemini/skills/kubernetes-deploy/SKILL.md`, `.gemini/skills/observability/SKILL.md`, `.gemini/skills/git-workflow/SKILL.md`, `.gemini/skills/systematic-debugging/SKILL.md`, `.gemini/skills/typescript-best-practices/SKILL.md`, `.gemini/skills/javascript-best-practices/SKILL.md`, `.gemini/skills/python-best-practices/SKILL.md`.
+- Local skill file hints if installed: `.agents/skills/ci-cd-pipeline/SKILL.md`, `.agents/skills/kubernetes-deploy/SKILL.md`, `.agents/skills/observability/SKILL.md`, `.agents/skills/git-workflow/SKILL.md`, `.agents/skills/systematic-debugging/SKILL.md`, `.agents/skills/typescript-best-practices/SKILL.md`, `.agents/skills/javascript-best-practices/SKILL.md`, `.agents/skills/python-best-practices/SKILL.md`.
 - Treat the skill bundle as already resolved for this workflow. Do not start with route discovery.
-3. Confirm the request fits the workflow's "When to use" section.
+3. Confirm the request fits the workflow's "When to use" section before acting.
 4. Execute according to "Workflow steps" and apply "Context notes".
 5. Complete "Verification" checks and report concrete evidence.
-6. If freshness, public comparison, or explicit research needs appear, pause implementation and load `deep-research` or route to the researcher posture first.
+6. If freshness, public comparison, or explicit research needs appear, pause implementation and load `deep-research` or route to research first.
 7. For outside evidence: repo first, official docs next, Reddit/community only as labeled secondary evidence.
 
+Workflow source:
+# DevOps Workflow
+
+## When to use
+
+Use this for deployment automation, CI/CD pipeline changes, incident response, or infrastructure operations.
+
+## Routing
+
+- Primary specialist: `@devops-engineer`
+- Reliability support: `@sre-engineer`
+- Verification support: `@validator`
+
+## Context notes
+
+- This workflow file, active platform rules, and selected agents or skills guide execution.
+- Attach deployment targets, pipeline configs, incident details, and infrastructure specs.
+
+## Skill Routing
+
+- Primary skills: `devops-engineer`, `ci-cd-pipelines`, `docker-kubernetes`
+- Supporting skills (optional): `sre-engineer`, `observability`, `serverless-patterns`, `git-workflow`, `debugging-strategies`, `typescript-pro`, `javascript-pro`, `python-pro`, `golang-pro`
+- Start with `devops-engineer` for operational patterns. Add `ci-cd-pipelines` for pipeline work, `docker-kubernetes` for container operations, `sre-engineer` for incident response, `serverless-patterns` for serverless infrastructure.
+
+## Workflow steps
+
+1. Assess current state and change scope.
+2. Plan change with rollback strategy.
+3. Apply change in staged manner (dev → staging → production).
+4. Verify health at each stage before proceeding.
+5. Document operational procedures and runbooks.
+
+## Verification
+
+- Change applied successfully with no service degradation.
+- Rollback procedure verified or documented.
+- Monitoring confirms normal operation after change.
+- Runbook updated for new procedures.
+
+## Output Contract
+
+```yaml
+DEVOPS_WORKFLOW_RESULT:
+  primary_agent: devops-engineer
+  supporting_agents: [sre-engineer?, validator?]
+  primary_skills: [devops-engineer, ci-cd-pipelines, docker-kubernetes]
+  supporting_skills: [sre-engineer?, observability?, serverless-patterns?]
+  change:
+    description: <string>
+    blast_radius: <string>
+    rollback_plan: <string>
+  execution:
+    stages_completed: [<string>]
+    health_checks: [<string>]
+  operational_docs: [<string>] | []
+  follow_up_items: [<string>] | []
+```
+
 If command arguments are provided, treat them as additional user context.
 '''

package/workflows/workflows/agent-environment-setup/platforms/gemini/commands/implement-track.toml

@@ -1,19 +1,86 @@
 description = "Execute large work in milestones with explicit quality gates and status updates."
 prompt = '''
-Follow the /implement-track workflow from .gemini/workflows/implement-track.md.
+Execute the native projection of the /implement-track workflow.
+
+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: `.gemini/skills/system-design/SKILL.md`, `.gemini/skills/api-design/SKILL.md`, `.gemini/skills/database-design/SKILL.md`, `.gemini/skills/typescript-best-practices/SKILL.md`, `.gemini/skills/javascript-best-practices/SKILL.md`, `.gemini/skills/python-best-practices/SKILL.md`, `.gemini/skills/golang-best-practices/SKILL.md`, `.gemini/skills/react/SKILL.md`.
+- Local skill file hints if installed: `.agents/skills/system-design/SKILL.md`, `.agents/skills/api-design/SKILL.md`, `.agents/skills/database-design/SKILL.md`, `.agents/skills/typescript-best-practices/SKILL.md`, `.agents/skills/javascript-best-practices/SKILL.md`, `.agents/skills/python-best-practices/SKILL.md`, `.agents/skills/golang-best-practices/SKILL.md`, `.agents/skills/react/SKILL.md`.
 - Treat the skill bundle as already resolved for this workflow. Do not start with route discovery.
-3. Confirm the request fits the workflow's "When to use" section.
+3. Confirm the request fits the workflow's "When to use" section before acting.
 4. Execute according to "Workflow steps" and apply "Context notes".
 5. Complete "Verification" checks and report concrete evidence.
-6. If freshness, public comparison, or explicit research needs appear, pause implementation and load `deep-research` or route to the researcher posture first.
+6. If freshness, public comparison, or explicit research needs appear, pause implementation and load `deep-research` or route to research first.
 7. For outside evidence: repo first, official docs next, Reddit/community only as labeled secondary evidence.
 
+Workflow source:
+# Implement Track Workflow
+
+## When to use
+
+Use this for large-scale implementation work that spans multiple sessions or milestones and needs progress tracking with quality gates.
+
+## Routing
+
+- Primary coordinator: `@orchestrator`
+- Implementation agents: determined by task domain
+- Quality gate: `@validator`
+
+## Context notes
+
+- This workflow file, active platform rules, and selected agents or skills guide execution.
+- Attach the implementation plan, milestone definitions, and acceptance criteria per milestone.
+- Reuse `docs/specs/<spec-id>/` when present instead of maintaining a separate progress source of truth.
+- Read `ENGINEERING_RULES.md` first and `docs/foundation/TECH.md` next before starting milestone execution. Use `## Build And Validation` for the validated build sequence and `## Key Commands` for test/lint commands.
+
+## Skill Routing
+
+- Primary skills: `system-design`, `api-design`
+- 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
+
+1. Review implementation plan and confirm milestone boundaries.
+2. Execute current milestone with focused implementation.
+3. Run quality gate validation at milestone completion.
+4. Update progress tracking and capture status.
+5. Adjust remaining plan, spec traceability, and doc refresh needs based on learnings.
+6. Proceed to next milestone or report completion.
+
+## Verification
+
+- Each milestone has clear acceptance criteria that are verified.
+- Quality gate passed before proceeding to next milestone.
+- Progress tracker updated with evidence of completion.
+- Remaining milestones adjusted for any scope changes.
+
+## Output Contract
+
+```yaml
+IMPLEMENT_TRACK_WORKFLOW_RESULT:
+  primary_agent: orchestrator
+  supporting_agents: [<milestone-agents>]
+  primary_skills: [system-design, api-design]
+  supporting_skills: [database-design?, typescript-pro?, javascript-pro?, python-pro?, golang-pro?, react-expert?, nextjs-developer?]
+  milestones:
+    - id: <milestone-id>
+      description: <string>
+      status: completed | in_progress | pending
+      acceptance_criteria_met: [<string>]
+      validation_evidence: <string>
+  overall_progress: <percentage>
+  scope_changes: [<string>] | []
+  spec_id: <string> | null
+  spec_root: docs/specs/<spec-id> | null
+  traceability_status: complete | partial | blocked
+  doc_impact: none | tech | rules | both
+  follow_up_items: [<string>] | []
+```
+
 If command arguments are provided, treat them as additional user context.
 '''

package/workflows/workflows/agent-environment-setup/platforms/gemini/commands/migrate.toml

@@ -1,19 +1,85 @@
 description = "Plan and execute technology migrations, framework upgrades, and dependency updates with rollback safety, incremental verification, and zero-downtime transition."
 prompt = '''
-Follow the /migrate workflow from .gemini/workflows/migrate.md.
+Execute the native projection of the /migrate workflow.
+
+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: `.gemini/skills/system-design/SKILL.md`, `.gemini/skills/code-review/SKILL.md`, `.gemini/skills/unit-testing/SKILL.md`, `.gemini/skills/typescript-best-practices/SKILL.md`, `.gemini/skills/javascript-best-practices/SKILL.md`, `.gemini/skills/python-best-practices/SKILL.md`, `.gemini/skills/golang-best-practices/SKILL.md`.
+- Local skill file hints if installed: `.agents/skills/system-design/SKILL.md`, `.agents/skills/code-review/SKILL.md`, `.agents/skills/unit-testing/SKILL.md`, `.agents/skills/typescript-best-practices/SKILL.md`, `.agents/skills/javascript-best-practices/SKILL.md`, `.agents/skills/python-best-practices/SKILL.md`, `.agents/skills/golang-best-practices/SKILL.md`.
 - Treat the skill bundle as already resolved for this workflow. Do not start with route discovery.
-3. Confirm the request fits the workflow's "When to use" section.
+3. Confirm the request fits the workflow's "When to use" section before acting.
 4. Execute according to "Workflow steps" and apply "Context notes".
 5. Complete "Verification" checks and report concrete evidence.
-6. If freshness, public comparison, or explicit research needs appear, pause implementation and load `deep-research` or route to the researcher posture first.
+6. If freshness, public comparison, or explicit research needs appear, pause implementation and load `deep-research` or route to research first.
 7. For outside evidence: repo first, official docs next, Reddit/community only as labeled secondary evidence.
 
+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>] | []
+```
+
 If command arguments are provided, treat them as additional user context.
 '''