@cubis/foundry 0.3.77 → 0.3.78

package/workflows/skills/generated/skill-audit.json

@@ -2,7 +2,7 @@
   "$schema": "cubis-foundry-skill-audit-v1",
   "generatedAt": "1970-01-01T00:00:00.000Z",
   "summary": {
-    "keep": 69,
+    "keep": 70,
     "review": 0,
     "alias-only": 0
   },
@@ -502,6 +502,15 @@
       "tier": "system",
       "reason": "Canonical skill remains active in the layered catalog."
     },
+    {
+      "id": "spec-driven-delivery",
+      "canonical_id": "spec-driven-delivery",
+      "status": "keep",
+      "layer": "workflow-specialists",
+      "category": "workflow-specialists",
+      "tier": "experimental",
+      "reason": "Canonical skill remains active in the layered catalog."
+    },
     {
       "id": "spring-boot",
       "canonical_id": "spring-boot",
@@ -629,5 +638,5 @@
       "reason": "Canonical skill remains active in the layered catalog."
     }
   ],
-  "contentHash": "101f661a3eeb90cd"
+  "contentHash": "e89ff93cdf3025e8"
 }

package/workflows/skills/generated/skill-catalog.json

@@ -2,10 +2,10 @@
   "$schema": "cubis-foundry-skill-catalog-v1",
   "generatedAt": "1970-01-01T00:00:00.000Z",
   "summary": {
-    "totalEntries": 69,
-    "totalSkills": 69,
+    "totalEntries": 70,
+    "totalSkills": 70,
     "totalSubskills": 0,
-    "canonicalSkills": 69,
+    "canonicalSkills": 70,
     "compatibilityAliases": 0,
     "layers": [
       "core-operating",
@@ -1748,6 +1748,40 @@
         "core-operating"
       ]
     },
+    {
+      "id": "spec-driven-delivery",
+      "package_id": "spec-driven-delivery",
+      "catalog_id": "spec-driven-delivery",
+      "kind": "skill",
+      "path": "workflows/skills/spec-driven-delivery/SKILL.md",
+      "name": "spec-driven-delivery",
+      "description": "Use when turning a non-trivial request into a Git-tracked spec pack, maintaining traceability during execution, and updating specs before code when requirements or architecture change.",
+      "canonical": true,
+      "canonical_id": "spec-driven-delivery",
+      "deprecated": false,
+      "replaced_by": null,
+      "aliases": [],
+      "category": "workflow-specialists",
+      "layer": "workflow-specialists",
+      "maturity": "incubating",
+      "tier": "experimental",
+      "tags": [
+        "delivery",
+        "driven",
+        "spec",
+        "spec driven delivery",
+        "spec-driven-delivery",
+        "workflow-specialists"
+      ],
+      "triggers": [
+        "spec-driven-delivery",
+        "spec driven delivery",
+        "spec",
+        "driven",
+        "delivery",
+        "workflow-specialists"
+      ]
+    },
     {
       "id": "spring-boot",
       "package_id": "spring-boot",
@@ -2173,5 +2207,5 @@
       ]
     }
   ],
-  "contentHash": "b27e549d17f95efb"
+  "contentHash": "b8ed402a6bbe2ed2"
 }

package/workflows/skills/skills_index.json

@@ -1721,6 +1721,40 @@
       "core-operating"
     ]
   },
+  {
+    "id": "spec-driven-delivery",
+    "package_id": "spec-driven-delivery",
+    "catalog_id": "spec-driven-delivery",
+    "kind": "skill",
+    "name": "spec-driven-delivery",
+    "canonical": true,
+    "canonical_id": "spec-driven-delivery",
+    "deprecated": false,
+    "replaced_by": null,
+    "aliases": [],
+    "category": "workflow-specialists",
+    "layer": "workflow-specialists",
+    "maturity": "incubating",
+    "tier": "experimental",
+    "tags": [
+      "delivery",
+      "driven",
+      "spec",
+      "spec driven delivery",
+      "spec-driven-delivery",
+      "workflow-specialists"
+    ],
+    "path": ".agents/skills/spec-driven-delivery/SKILL.md",
+    "description": "Use when turning a non-trivial request into a Git-tracked spec pack, maintaining traceability during execution, and updating specs before code when requirements or architecture change.",
+    "triggers": [
+      "spec-driven-delivery",
+      "spec driven delivery",
+      "spec",
+      "driven",
+      "delivery",
+      "workflow-specialists"
+    ]
+  },
   {
     "id": "spring-boot",
     "package_id": "spring-boot",

package/workflows/skills/spec-driven-delivery/SKILL.md

@@ -0,0 +1,63 @@
+---
+name: spec-driven-delivery
+description: Use when turning a non-trivial request into a Git-tracked spec pack, maintaining traceability during execution, and updating specs before code when requirements or architecture change.
+license: MIT
+metadata:
+  author: cubis-foundry
+  version: "1.0"
+compatibility: Claude Code, Codex, GitHub Copilot
+---
+
+# Spec-Driven Delivery
+
+## Purpose
+
+Create and maintain a lightweight source of truth for non-trivial work. This skill turns requirements, decisions, acceptance criteria, and architecture impact into a spec pack under the `docs/specs/<spec-id>/` workspace area, then keeps that pack aligned as implementation evolves.
+
+## When to Use
+
+- Planning a medium or large feature before implementation
+- Capturing acceptance criteria, traceability, and architecture impact in Git
+- Reusing or refreshing an existing spec pack for a follow-up change
+- Bridging native plan-mode output into durable project documents
+- Keeping implementation, verification, and documentation aligned across sessions
+
+## Instructions
+
+1. **Classify the task first** because trivial work should not pay spec overhead. Use this skill only when the task is multi-step, cross-session, cross-domain, risky, or likely to change architecture, testing strategy, or team coordination.
+2. **Look for an existing spec pack before creating a new one** because duplicate specs create drift. Reuse the closest matching spec directory when the current request extends an active initiative.
+3. **Create a stable `spec_id` and spec root** because the same identifier should survive planning, execution, review, and follow-up changes.
+4. **Write the minimum viable pack** because the goal is durable coordination, not bureaucracy. Keep the brief, acceptance, tasks, traceability, and handoff documents concise and testable.
+5. **Use `sadd` when turning requirements into assertions** because spec quality depends on extracting testable behavior instead of leaving requirements vague.
+6. **Record architecture impact explicitly** because implementation must stay aligned with the project architecture contract and current-state tech map. Mark whether the change affects architecture style, module boundaries, dependency rules, design system, deployment shape, or testing strategy.
+7. **Update the spec before implementation changes behavior** because traceability breaks when code changes first and docs lag behind.
+8. **Keep the task graph execution-ready** because `/implement-track` and `/orchestrate` should be able to act on the spec without replanning. Every task should have ownership, dependencies, acceptance criteria, and a verification path.
+9. **Route external research through `deep-research`** because repo-first planning still needs disciplined escalation when freshness or public comparison matters.
+10. **Emit a clear next route** because spec work usually hands off into `/create`, `/implement-track`, `/orchestrate`, or `/architecture`.
+11. **Report `doc_impact` and `traceability_status`** because feature work should surface whether the architecture contract or tech map must be refreshed at the end.
+12. **Keep the pack alive during execution** because a stale spec is worse than none. Update acceptance, tasks, and traceability when scope or constraints change.
+
+## Output Format
+
+Deliver:
+
+1. **Spec summary** — `spec_id`, `spec_root`, goal, scope, and why spec mode is warranted
+2. **Acceptance and traceability state** — requirements, open gaps, and `traceability_status`
+3. **Execution-ready plan** — tasks, owners, dependencies, and verification checkpoints
+4. **Architecture and doc impact** — `architecture_impact` plus `doc_impact`
+5. **Recommended next route** — exact workflow, agent, or skill to continue from the spec
+
+## References
+
+| File | Load when |
+| --- | --- |
+| `../sadd/SKILL.md` | Need requirement mining, GIVEN-WHEN-THEN specs, or traceability patterns. |
+| `../architecture-doc/SKILL.md` | Need ADRs, system boundaries, or architecture-document structure. |
+| `../deep-research/SKILL.md` | Need repo-first research escalation or evidence labeling rules. |
+
+## Examples
+
+| File | Use when |
+| --- | --- |
+| `../sadd/references/spec-mining.md` | Turning loose requirements into testable spec entries. |
+| `../sadd/references/coverage-mapping.md` | Building a traceability matrix that links specs, tests, and code. |

package/workflows/workflows/agent-environment-setup/generated/route-manifest.json

@@ -1,10 +1,10 @@
 {
   "$schema": "cubis-foundry-route-manifest-v1",
   "generatedAt": "1970-01-01T00:00:00.000Z",
-  "contentHash": "47cf8920e99d0258",
+  "contentHash": "84d671504acfd27c",
   "summary": {
-    "totalRoutes": 40,
-    "workflows": 18,
+    "totalRoutes": 42,
+    "workflows": 20,
     "agents": 22
   },
   "routes": [
@@ -1206,6 +1206,64 @@
         }
       }
     },
+    {
+      "kind": "workflow",
+      "id": "architecture",
+      "command": "/architecture",
+      "displayName": "architecture",
+      "description": "Refresh the project architecture contract and current-state map in ENGINEERING_RULES.md and TECH.md with explicit structure, design-system, testing, and flow guidance.",
+      "triggers": [
+        "architecture",
+        "design system",
+        "adr",
+        "clean architecture",
+        "system map",
+        "app structure",
+        "technical governance",
+        "flow diagram"
+      ],
+      "primaryAgent": "project-planner",
+      "supportingAgents": [
+        "documentation-writer",
+        "researcher",
+        "backend-specialist",
+        "frontend-specialist",
+        "database-architect"
+      ],
+      "primarySkills": [
+        "architecture-doc",
+        "system-design",
+        "tech-doc",
+        "frontend-design"
+      ],
+      "supportingSkills": [
+        "api-design",
+        "database-design",
+        "sadd",
+        "deep-research"
+      ],
+      "artifacts": {
+        "codex": {
+          "workflowFile": "architecture.md",
+          "compatibilityAlias": "$workflow-architecture"
+        },
+        "copilot": {
+          "workflowFile": "architecture.md",
+          "promptFile": "workflow-architecture.prompt.md"
+        },
+        "antigravity": {
+          "workflowFile": "architecture.md",
+          "commandFile": "architecture.toml"
+        },
+        "claude": {
+          "workflowFile": "architecture.md"
+        },
+        "gemini": {
+          "workflowFile": "architecture.md",
+          "commandFile": "architecture.toml"
+        }
+      }
+    },
     {
       "kind": "workflow",
       "id": "backend",
@@ -1792,7 +1850,6 @@
       "description": "Build a decision-complete implementation plan with interfaces, failure modes, and acceptance criteria.",
       "triggers": [
         "plan",
-        "spec",
         "design",
         "roadmap",
         "acceptance",
@@ -2061,6 +2118,62 @@
         }
       }
     },
+    {
+      "kind": "workflow",
+      "id": "spec",
+      "command": "/spec",
+      "displayName": "spec",
+      "description": "Create or refresh a Git-tracked spec pack for non-trivial work, including acceptance criteria, traceability, architecture impact, and next-route handoff.",
+      "triggers": [
+        "spec",
+        "sdd",
+        "source of truth",
+        "traceability",
+        "acceptance criteria",
+        "openspec",
+        "requirements",
+        "architecture impact"
+      ],
+      "primaryAgent": "project-planner",
+      "supportingAgents": [
+        "researcher",
+        "orchestrator",
+        "documentation-writer"
+      ],
+      "primarySkills": [
+        "spec-driven-delivery",
+        "sadd"
+      ],
+      "supportingSkills": [
+        "system-design",
+        "architecture-doc",
+        "deep-research",
+        "api-design",
+        "database-design",
+        "tech-doc"
+      ],
+      "artifacts": {
+        "codex": {
+          "workflowFile": "spec.md",
+          "compatibilityAlias": "$workflow-spec"
+        },
+        "copilot": {
+          "workflowFile": "spec.md",
+          "promptFile": "workflow-spec.prompt.md"
+        },
+        "antigravity": {
+          "workflowFile": "spec.md",
+          "commandFile": "spec.toml"
+        },
+        "claude": {
+          "workflowFile": "spec.md"
+        },
+        "gemini": {
+          "workflowFile": "spec.md",
+          "commandFile": "spec.toml"
+        }
+      }
+    },
     {
       "kind": "workflow",
       "id": "test",

package/workflows/workflows/agent-environment-setup/manifest.json

@@ -6,6 +6,7 @@
     "antigravity": {
       "workflows": [
         "accessibility.md",
+        "architecture.md",
         "backend.md",
         "create.md",
         "database.md",
@@ -21,6 +22,7 @@
         "release.md",
         "review.md",
         "security.md",
+        "spec.md",
         "test.md",
         "vercel.md"
       ],
@@ -104,6 +106,7 @@
         "sanitize-pii",
         "secret-management",
         "skill-creator",
+        "spec-driven-delivery",
         "spring-boot",
         "sqlalchemy",
         "stitch",
@@ -129,6 +132,7 @@
       ],
       "commands": [
         "accessibility.toml",
+        "architecture.toml",
         "backend.toml",
         "create.toml",
         "database.toml",
@@ -144,6 +148,7 @@
         "release.toml",
         "review.toml",
         "security.toml",
+        "spec.toml",
         "test.toml",
         "vercel.toml"
       ]
@@ -151,6 +156,7 @@
     "codex": {
       "workflows": [
         "accessibility.md",
+        "architecture.md",
         "backend.md",
         "create.md",
         "database.md",
@@ -166,6 +172,7 @@
         "release.md",
         "review.md",
         "security.md",
+        "spec.md",
         "test.md",
         "vercel.md"
       ],
@@ -249,6 +256,7 @@
         "sanitize-pii",
         "secret-management",
         "skill-creator",
+        "spec-driven-delivery",
         "spring-boot",
         "sqlalchemy",
         "stitch",
@@ -276,6 +284,7 @@
     "copilot": {
       "workflows": [
         "accessibility.md",
+        "architecture.md",
         "backend.md",
         "create.md",
         "database.md",
@@ -291,6 +300,7 @@
         "release.md",
         "review.md",
         "security.md",
+        "spec.md",
         "test.md",
         "vercel.md"
       ],
@@ -374,6 +384,7 @@
         "sanitize-pii",
         "secret-management",
         "skill-creator",
+        "spec-driven-delivery",
         "spring-boot",
         "sqlalchemy",
         "stitch",
@@ -399,6 +410,7 @@
       ],
       "prompts": [
         "workflow-accessibility.prompt.md",
+        "workflow-architecture.prompt.md",
         "workflow-backend.prompt.md",
         "workflow-create.prompt.md",
         "workflow-database.prompt.md",
@@ -414,6 +426,7 @@
         "workflow-release.prompt.md",
         "workflow-review.prompt.md",
         "workflow-security.prompt.md",
+        "workflow-spec.prompt.md",
         "workflow-test.prompt.md",
         "workflow-vercel.prompt.md"
       ]
@@ -421,6 +434,7 @@
     "claude": {
       "workflows": [
         "accessibility.md",
+        "architecture.md",
         "backend.md",
         "create.md",
         "database.md",
@@ -436,6 +450,7 @@
         "release.md",
         "review.md",
         "security.md",
+        "spec.md",
         "test.md",
         "vercel.md"
       ],
@@ -519,6 +534,7 @@
         "sanitize-pii",
         "secret-management",
         "skill-creator",
+        "spec-driven-delivery",
         "spring-boot",
         "sqlalchemy",
         "stitch",
@@ -567,6 +583,7 @@
     "gemini": {
       "workflows": [
         "accessibility.md",
+        "architecture.md",
         "backend.md",
         "create.md",
         "database.md",
@@ -582,6 +599,7 @@
         "release.md",
         "review.md",
         "security.md",
+        "spec.md",
         "test.md",
         "vercel.md"
       ],
@@ -642,6 +660,7 @@
         "sanitize-pii",
         "secret-management",
         "skill-creator",
+        "spec-driven-delivery",
         "spring-boot",
         "sqlalchemy",
         "stitch",
@@ -667,6 +686,7 @@
       ],
       "commands": [
         "accessibility.toml",
+        "architecture.toml",
         "backend.toml",
         "create.toml",
         "database.toml",
@@ -682,6 +702,7 @@
         "release.toml",
         "review.toml",
         "security.toml",
+        "spec.toml",
         "test.toml",
         "vercel.toml"
       ]

package/workflows/workflows/agent-environment-setup/platforms/antigravity/commands/accessibility.toml

@@ -4,11 +4,16 @@ Follow the /accessibility workflow from .agent/workflows/accessibility.md.
 
 Execution contract:
 1. Treat route selection as already resolved by this command; do not begin with skill discovery.
-2. Confirm the request fits the workflow's "When to use" section.
-3. Execute according to "Workflow steps" and apply "Context notes".
-4. Complete "Verification" checks and report concrete evidence.
-5. If freshness, public comparison, or explicit research needs appear, pause implementation and load `deep-research` or hand off to `@researcher` first.
-6. For outside evidence: repo first, official docs next, Reddit/community only as labeled secondary evidence.
+2. Read `ENGINEERING_RULES.md` first and `TECH.md` next when they exist before non-trivial execution.
+Attached skills:
+- Load these exact skill IDs first: `code-review`, `frontend-design`, `performance-testing`, `react`, `nextjs`, `playwright-interactive`, `typescript-best-practices`, `javascript-best-practices`.
+- Local skill file hints if installed: `.agent/skills/code-review/SKILL.md`, `.agent/skills/frontend-design/SKILL.md`, `.agent/skills/performance-testing/SKILL.md`, `.agent/skills/react/SKILL.md`, `.agent/skills/nextjs/SKILL.md`, `.agent/skills/playwright-interactive/SKILL.md`, `.agent/skills/typescript-best-practices/SKILL.md`, `.agent/skills/javascript-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.
+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 hand off to `@researcher` first.
+7. For outside evidence: repo first, official docs next, Reddit/community only as labeled secondary evidence.
 
 If command arguments are provided, treat them as additional user context.
 '''

package/workflows/workflows/agent-environment-setup/platforms/antigravity/commands/architecture.toml

@@ -0,0 +1,19 @@
+description = "Refresh the project architecture contract and current-state map in ENGINEERING_RULES.md and TECH.md with explicit structure, design-system, testing, and flow guidance."
+prompt = '''
+Follow the /architecture workflow from .agent/workflows/architecture.md.
+
+Execution contract:
+1. Treat route selection as already resolved by this command; do not begin with skill discovery.
+2. Read `ENGINEERING_RULES.md` first and `TECH.md` next when they exist before non-trivial execution.
+Attached skills:
+- Load these exact skill IDs first: `architecture-doc`, `system-design`, `tech-doc`, `frontend-design`, `api-design`, `database-design`, `sadd`, `deep-research`.
+- Local skill file hints if installed: `.agent/skills/architecture-doc/SKILL.md`, `.agent/skills/system-design/SKILL.md`, `.agent/skills/tech-doc/SKILL.md`, `.agent/skills/frontend-design/SKILL.md`, `.agent/skills/api-design/SKILL.md`, `.agent/skills/database-design/SKILL.md`, `.agent/skills/sadd/SKILL.md`, `.agent/skills/deep-research/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.
+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 hand off to `@researcher` first.
+7. For outside evidence: repo first, official docs next, Reddit/community only as labeled secondary evidence.
+
+If command arguments are provided, treat them as additional user context.
+'''

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

@@ -4,11 +4,16 @@ Follow the /backend workflow from .agent/workflows/backend.md.
 
 Execution contract:
 1. Treat route selection as already resolved by this command; do not begin with skill discovery.
-2. Confirm the request fits the workflow's "When to use" section.
-3. Execute according to "Workflow steps" and apply "Context notes".
-4. Complete "Verification" checks and report concrete evidence.
-5. If freshness, public comparison, or explicit research needs appear, pause implementation and load `deep-research` or hand off to `@researcher` first.
-6. For outside evidence: repo first, official docs next, Reddit/community only as labeled secondary evidence.
+2. Read `ENGINEERING_RULES.md` first and `TECH.md` next 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: `.agent/skills/api-design/SKILL.md`, `.agent/skills/javascript-best-practices/SKILL.md`, `.agent/skills/owasp-security-review/SKILL.md`, `.agent/skills/database-design/SKILL.md`, `.agent/skills/nestjs/SKILL.md`, `.agent/skills/fastapi/SKILL.md`, `.agent/skills/microservices-design/SKILL.md`, `.agent/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.
+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 hand off to `@researcher` first.
+7. For outside evidence: repo first, official docs next, Reddit/community only as labeled secondary evidence.
 
 If command arguments are provided, treat them as additional user context.
 '''

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

@@ -4,11 +4,16 @@ Follow the /create workflow from .agent/workflows/create.md.
 
 Execution contract:
 1. Treat route selection as already resolved by this command; do not begin with skill discovery.
-2. Confirm the request fits the workflow's "When to use" section.
-3. Execute according to "Workflow steps" and apply "Context notes".
-4. Complete "Verification" checks and report concrete evidence.
-5. If freshness, public comparison, or explicit research needs appear, pause implementation and load `deep-research` or hand off to `@researcher` first.
-6. For outside evidence: repo first, official docs next, Reddit/community only as labeled secondary evidence.
+2. Read `ENGINEERING_RULES.md` first and `TECH.md` next 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: `.agent/skills/typescript-best-practices/SKILL.md`, `.agent/skills/javascript-best-practices/SKILL.md`, `.agent/skills/python-best-practices/SKILL.md`, `.agent/skills/golang-best-practices/SKILL.md`, `.agent/skills/java-best-practices/SKILL.md`, `.agent/skills/csharp-best-practices/SKILL.md`, `.agent/skills/kotlin-best-practices/SKILL.md`, `.agent/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.
+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 hand off to `@researcher` first.
+7. For outside evidence: repo first, official docs next, Reddit/community only as labeled secondary evidence.
 
 If command arguments are provided, treat them as additional user context.
 '''

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

@@ -4,11 +4,16 @@ Follow the /database workflow from .agent/workflows/database.md.
 
 Execution contract:
 1. Treat route selection as already resolved by this command; do not begin with skill discovery.
-2. Confirm the request fits the workflow's "When to use" section.
-3. Execute according to "Workflow steps" and apply "Context notes".
-4. Complete "Verification" checks and report concrete evidence.
-5. If freshness, public comparison, or explicit research needs appear, pause implementation and load `deep-research` or hand off to `@researcher` first.
-6. For outside evidence: repo first, official docs next, Reddit/community only as labeled secondary evidence.
+2. Read `ENGINEERING_RULES.md` first and `TECH.md` next 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: `.agent/skills/database-design/SKILL.md`, `.agent/skills/drizzle-orm/SKILL.md`, `.agent/skills/typescript-best-practices/SKILL.md`, `.agent/skills/javascript-best-practices/SKILL.md`, `.agent/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.
+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 hand off to `@researcher` first.
+7. For outside evidence: repo first, official docs next, Reddit/community only as labeled secondary evidence.
 
 If command arguments are provided, treat them as additional user context.
 '''

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

@@ -4,11 +4,16 @@ Follow the /debug workflow from .agent/workflows/debug.md.
 
 Execution contract:
 1. Treat route selection as already resolved by this command; do not begin with skill discovery.
-2. Confirm the request fits the workflow's "When to use" section.
-3. Execute according to "Workflow steps" and apply "Context notes".
-4. Complete "Verification" checks and report concrete evidence.
-5. If freshness, public comparison, or explicit research needs appear, pause implementation and load `deep-research` or hand off to `@researcher` first.
-6. For outside evidence: repo first, official docs next, Reddit/community only as labeled secondary evidence.
+2. Read `ENGINEERING_RULES.md` first and `TECH.md` next 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: `.agent/skills/systematic-debugging/SKILL.md`, `.agent/skills/observability/SKILL.md`, `.agent/skills/unit-testing/SKILL.md`, `.agent/skills/typescript-best-practices/SKILL.md`, `.agent/skills/javascript-best-practices/SKILL.md`, `.agent/skills/python-best-practices/SKILL.md`, `.agent/skills/golang-best-practices/SKILL.md`, `.agent/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.
+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 hand off to `@researcher` first.
+7. For outside evidence: repo first, official docs next, Reddit/community only as labeled secondary evidence.
 
 If command arguments are provided, treat them as additional user context.
 '''