@cubis/foundry 0.3.76 → 0.3.78

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": "9aedd9bfd58f1f59",
+  "contentHash": "84d671504acfd27c",
   "summary": {
-    "totalRoutes": 40,
-    "workflows": 18,
+    "totalRoutes": 42,
+    "workflows": 20,
     "agents": 22
   },
   "routes": [
@@ -498,7 +498,7 @@
       ],
       "supportingSkills": [
         "database-design",
-        "architecture-doc",
+        "deep-research",
         "mcp-server-builder",
         "tech-doc",
         "prompt-engineering",
@@ -701,7 +701,7 @@
       ],
       "supportingSkills": [
         "database-design",
-        "architecture-doc",
+        "deep-research",
         "mcp-server-builder",
         "tech-doc",
         "prompt-engineering",
@@ -804,7 +804,7 @@
       "primaryAgent": "researcher",
       "supportingAgents": [],
       "primarySkills": [
-        "architecture-doc",
+        "deep-research",
         "system-design"
       ],
       "supportingSkills": [
@@ -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",
@@ -1694,7 +1752,7 @@
         "frontend-specialist"
       ],
       "primarySkills": [
-        "architecture-doc",
+        "deep-research",
         "system-design"
       ],
       "supportingSkills": [
@@ -1756,7 +1814,7 @@
       ],
       "supportingSkills": [
         "database-design",
-        "architecture-doc",
+        "deep-research",
         "mcp-server-builder",
         "tech-doc",
         "prompt-engineering",
@@ -1792,7 +1850,6 @@
       "description": "Build a decision-complete implementation plan with interfaces, failure modes, and acceptance criteria.",
       "triggers": [
         "plan",
-        "spec",
         "design",
         "roadmap",
         "acceptance",
@@ -1815,7 +1872,7 @@
       ],
       "supportingSkills": [
         "database-design",
-        "architecture-doc",
+        "deep-research",
         "mcp-server-builder",
         "tech-doc",
         "prompt-engineering",
@@ -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

@@ -1,11 +1,12 @@
 {
   "id": "agent-environment-setup",
-  "version": "1.4.0",
+  "version": "1.5.0",
   "description": "Workflow-first AI agent environment setup for Antigravity, Codex, Copilot, Claude Code, and Gemini CLI.",
   "platforms": {
     "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"
       ],
@@ -55,6 +57,7 @@
         "code-review",
         "csharp-best-practices",
         "database-design",
+        "deep-research",
         "django-drf",
         "docker-compose-dev",
         "drizzle-orm",
@@ -103,6 +106,7 @@
         "sanitize-pii",
         "secret-management",
         "skill-creator",
+        "spec-driven-delivery",
         "spring-boot",
         "sqlalchemy",
         "stitch",
@@ -128,6 +132,7 @@
       ],
       "commands": [
         "accessibility.toml",
+        "architecture.toml",
         "backend.toml",
         "create.toml",
         "database.toml",
@@ -143,6 +148,7 @@
         "release.toml",
         "review.toml",
         "security.toml",
+        "spec.toml",
         "test.toml",
         "vercel.toml"
       ]
@@ -150,6 +156,7 @@
     "codex": {
       "workflows": [
         "accessibility.md",
+        "architecture.md",
         "backend.md",
         "create.md",
         "database.md",
@@ -165,6 +172,7 @@
         "release.md",
         "review.md",
         "security.md",
+        "spec.md",
         "test.md",
         "vercel.md"
       ],
@@ -199,6 +207,7 @@
         "code-review",
         "csharp-best-practices",
         "database-design",
+        "deep-research",
         "django-drf",
         "docker-compose-dev",
         "drizzle-orm",
@@ -247,6 +256,7 @@
         "sanitize-pii",
         "secret-management",
         "skill-creator",
+        "spec-driven-delivery",
         "spring-boot",
         "sqlalchemy",
         "stitch",
@@ -274,6 +284,7 @@
     "copilot": {
       "workflows": [
         "accessibility.md",
+        "architecture.md",
         "backend.md",
         "create.md",
         "database.md",
@@ -289,6 +300,7 @@
         "release.md",
         "review.md",
         "security.md",
+        "spec.md",
         "test.md",
         "vercel.md"
       ],
@@ -323,6 +335,7 @@
         "code-review",
         "csharp-best-practices",
         "database-design",
+        "deep-research",
         "django-drf",
         "docker-compose-dev",
         "drizzle-orm",
@@ -371,6 +384,7 @@
         "sanitize-pii",
         "secret-management",
         "skill-creator",
+        "spec-driven-delivery",
         "spring-boot",
         "sqlalchemy",
         "stitch",
@@ -396,6 +410,7 @@
       ],
       "prompts": [
         "workflow-accessibility.prompt.md",
+        "workflow-architecture.prompt.md",
         "workflow-backend.prompt.md",
         "workflow-create.prompt.md",
         "workflow-database.prompt.md",
@@ -411,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"
       ]
@@ -418,6 +434,7 @@
     "claude": {
       "workflows": [
         "accessibility.md",
+        "architecture.md",
         "backend.md",
         "create.md",
         "database.md",
@@ -433,6 +450,7 @@
         "release.md",
         "review.md",
         "security.md",
+        "spec.md",
         "test.md",
         "vercel.md"
       ],
@@ -467,6 +485,7 @@
         "code-review",
         "csharp-best-practices",
         "database-design",
+        "deep-research",
         "django-drf",
         "docker-compose-dev",
         "drizzle-orm",
@@ -515,6 +534,7 @@
         "sanitize-pii",
         "secret-management",
         "skill-creator",
+        "spec-driven-delivery",
         "spring-boot",
         "sqlalchemy",
         "stitch",
@@ -536,12 +556,34 @@
           "type": "conductor-reference",
           "optional": true,
           "description": "If Conductor artifacts exist, workflows can reference them as supporting context."
+        },
+        {
+          "type": "template",
+          "event": "UserPromptSubmit",
+          "file": "README.md",
+          "optional": true,
+          "description": "Usage guide for the Claude route/research hook templates."
+        },
+        {
+          "type": "template",
+          "event": "UserPromptSubmit",
+          "file": "settings.snippet.json",
+          "optional": true,
+          "description": "Settings snippet that wires the route/research reminder hook into Claude Code."
+        },
+        {
+          "type": "template",
+          "event": "UserPromptSubmit",
+          "file": "route-research-guard.mjs",
+          "optional": true,
+          "description": "Hook script template that reinforces explicit-route honoring and research escalation."
         }
       ]
     },
     "gemini": {
       "workflows": [
         "accessibility.md",
+        "architecture.md",
         "backend.md",
         "create.md",
         "database.md",
@@ -557,6 +599,7 @@
         "release.md",
         "review.md",
         "security.md",
+        "spec.md",
         "test.md",
         "vercel.md"
       ],
@@ -568,6 +611,7 @@
         "code-review",
         "csharp-best-practices",
         "database-design",
+        "deep-research",
         "django-drf",
         "docker-compose-dev",
         "drizzle-orm",
@@ -616,6 +660,7 @@
         "sanitize-pii",
         "secret-management",
         "skill-creator",
+        "spec-driven-delivery",
         "spring-boot",
         "sqlalchemy",
         "stitch",
@@ -641,6 +686,7 @@
       ],
       "commands": [
         "accessibility.toml",
+        "architecture.toml",
         "backend.toml",
         "create.toml",
         "database.toml",
@@ -656,6 +702,7 @@
         "release.toml",
         "review.toml",
         "security.toml",
+        "spec.toml",
         "test.toml",
         "vercel.toml"
       ]

package/workflows/workflows/agent-environment-setup/platforms/antigravity/agents/orchestrator.md

@@ -5,7 +5,7 @@ tools: Read, Grep, Glob, Bash, Write, Edit
 model: inherit
 maxTurns: 30
 memory: project
-skills: system-design, api-design, database-design, architecture-doc, mcp-server-builder, tech-doc, prompt-engineering, skill-creator, typescript-best-practices, javascript-best-practices, python-best-practices
+skills: system-design, api-design, database-design, deep-research, mcp-server-builder, tech-doc, prompt-engineering, skill-creator, typescript-best-practices, javascript-best-practices, python-best-practices
 handoffs:
   - agent: "validator"
     title: "Validate Results"
@@ -31,8 +31,8 @@ Your only permitted actions:
 
 ## Skill Loading Contract
 
-- Do not call `skill_search` for `system-design`, `api-design`, `database-design`, `architecture-doc`, `mcp-server-builder`, `tech-doc`, `prompt-engineering`, or `skill-creator` when the task is clearly multi-stream coordination, planning, architecture design, contract design, research, or skill package work.
-- Use `system-design` when the coordination problem is really a design tradeoff problem, `api-design` when integration contracts are the coordination bottleneck, `database-design` when the shared dependency is a data-model or migration concern, `architecture-doc` when the coordination risk is stale or conflicting external information, `mcp-server-builder` for MCP-specific streams, `tech-doc` for OpenAI-doc verification streams, `prompt-engineering` for instruction-quality streams, and `skill-creator` when the coordinated changes are in skills, mirrors, routing, or packaging.
+- Do not call `skill_search` for `system-design`, `api-design`, `database-design`, `deep-research`, `mcp-server-builder`, `tech-doc`, `prompt-engineering`, or `skill-creator` when the task is clearly multi-stream coordination, planning, architecture design, contract design, research, or skill package work.
+- Use `system-design` when the coordination problem is really a design tradeoff problem, `api-design` when integration contracts are the coordination bottleneck, `database-design` when the shared dependency is a data-model or migration concern, `deep-research` when the coordination risk is stale or conflicting external information, `mcp-server-builder` for MCP-specific streams, `tech-doc` for OpenAI-doc verification streams, `prompt-engineering` for instruction-quality streams, and `skill-creator` when the coordinated changes are in skills, mirrors, routing, or packaging.
 - Prefer platform-native delegation features when available, but keep the orchestration contract stable even when execution stays in a single track.
 - Use `skill_validate` before `skill_get`, and use `skill_get_reference` only for the specific sidecar file needed by the current coordination step.
 
@@ -45,7 +45,7 @@ Load on demand. Do not preload all references.
 | `system-design` | Coordination depends on resolving system design or interface tradeoffs first.                             |
 | `api-design`          | The critical shared dependency is an API contract or integration boundary.                                |
 | `database-design`       | The coordination risk centers on schema, migration, data ownership, or engine choice.                     |
-| `architecture-doc`         | External sources, latest information, or public-repo comparisons are blocking confident execution.        |
+| `deep-research`         | External sources, latest information, or public-repo comparisons are blocking confident execution.        |
 | `mcp-server-builder`           | One stream is MCP server design, tool shape, or transport selection.                                      |
 | `tech-doc`           | One stream needs current OpenAI docs or version-specific behavior verification.                           |
 | `prompt-engineering`       | One stream is repairing prompts, agent rules, or instruction quality.                                     |
@@ -158,7 +158,8 @@ ANTI-LAZINESS:
 5. **Iterate, don't accept mediocrity** — if output is incomplete or wrong, re-delegate with feedback.
 6. **Track progress visibly** — maintain a task list showing status of each work item.
 7. **Fail fast on blockers** — if a dependency is missing or a task is stuck after 3 iterations, escalate.
-8. **Synthesize at the end** — combine outputs with concrete actions, risks, and verification evidence.
+8. **Route research explicitly** — when freshness or public comparison matters, delegate to `@researcher` or load `deep-research` before implementation.
+9. **Synthesize at the end** — combine outputs with concrete actions, risks, and verification evidence.
 
 ## Anti-Patterns to Prevent
 

package/workflows/workflows/agent-environment-setup/platforms/antigravity/agents/project-planner.md

@@ -5,7 +5,7 @@ tools: Read, Grep, Glob, Bash, Edit, Write
 model: inherit
 maxTurns: 30
 memory: project
-skills: system-design, api-design, database-design, architecture-doc, mcp-server-builder, tech-doc, prompt-engineering, skill-creator, typescript-best-practices, javascript-best-practices, python-best-practices
+skills: system-design, api-design, database-design, deep-research, mcp-server-builder, tech-doc, prompt-engineering, skill-creator, typescript-best-practices, javascript-best-practices, python-best-practices
 handoffs:
   - agent: "orchestrator"
     title: "Start Implementation"
@@ -24,7 +24,7 @@ Decompose complex requests into implementable plans with clear ownership, depend
 - Load `system-design` for system design tradeoffs in the plan.
 - Load `api-design` when the plan involves API contract decisions.
 - Load `database-design` when the plan involves data modeling or migration.
-- Load `architecture-doc` when planning requires external information or comparison.
+- Load `deep-research` when planning requires fresh external information, public comparison, or evidence beyond the repo.
 - Use `skill_validate` before `skill_get`, and use `skill_get_reference` only for the specific sidecar file needed.
 
 ## Skill References
@@ -34,7 +34,7 @@ Decompose complex requests into implementable plans with clear ownership, depend
 | `system-design` | Plan involves system design tradeoffs or component boundaries.     |
 | `api-design`          | Plan involves API contract decisions or integration points.        |
 | `database-design`       | Plan involves data modeling, schema design, or migration strategy. |
-| `architecture-doc`         | Planning requires external research or approach comparison.        |
+| `deep-research`         | Planning requires external research or approach comparison.        |
 | `mcp-server-builder`           | Plan involves MCP server or tool implementation.                   |
 | `skill-creator`         | Plan involves skill package creation or modification.              |
 
@@ -45,6 +45,7 @@ Decompose complex requests into implementable plans with clear ownership, depend
 - Every task needs an owner (agent), acceptance criteria, and verification approach.
 - Plan for rollback — every change should be reversible.
 - Front-load risk — tackle the hardest technical uncertainty first.
+- When outside evidence is needed, send research through `deep-research` first instead of mixing web browsing into every implementation stream.
 
 ## Planning Methodology
 

package/workflows/workflows/agent-environment-setup/platforms/antigravity/agents/researcher.md

@@ -18,7 +18,7 @@ tools: Read, Grep, Glob, Bash
 model: inherit
 maxTurns: 30
 memory: project
-skills: architecture-doc, system-design, database-design, tech-doc, prompt-engineering
+skills: deep-research, system-design, database-design, tech-doc, prompt-engineering
 handoffs:
   - agent: "project-planner"
     title: "Plan Implementation"
@@ -30,8 +30,8 @@ Investigate thoroughly, synthesize findings, and deliver structured knowledge be
 
 ## Skill Loading Contract
 
-- Do not call `skill_search` for `architecture-doc`, `system-design`, `database-design`, `tech-doc`, or `prompt-engineering` when the task is clearly research work.
-- Load `architecture-doc` first for all research tasks — it defines the research methodology.
+- Do not call `skill_search` for `deep-research`, `system-design`, `database-design`, `tech-doc`, or `prompt-engineering` when the task is clearly research work.
+- Load `deep-research` first for all research tasks — it defines the source ladder, evidence labeling, and research output contract.
 - Add `system-design` when research involves system design patterns or tradeoffs.
 - Add `database-design` when research involves data storage options or migration approaches.
 - Add `tech-doc` when research involves OpenAI API or model behavior verification.
@@ -42,7 +42,7 @@ Investigate thoroughly, synthesize findings, and deliver structured knowledge be
 
 | File                    | Load when                                                             |
 | ----------------------- | --------------------------------------------------------------------- |
-| `architecture-doc`         | All research tasks — defines the core research methodology.           |
+| `deep-research`         | All research tasks — defines the core research methodology.           |
 | `system-design` | Research involves system design patterns or architectural tradeoffs.  |
 | `database-design`       | Research involves data storage, database comparison, or migration.    |
 | `tech-doc`           | Research involves OpenAI API, model behavior, or version differences. |
@@ -51,6 +51,9 @@ Investigate thoroughly, synthesize findings, and deliver structured knowledge be
 ## Operating Stance
 
 - Breadth first, then depth — survey the landscape before drilling into specifics.
+- Repo first, then web — inspect local code, configs, and docs before using external sources.
+- Official docs first — use vendor or maintainer documentation as primary evidence.
+- Community evidence is secondary — Reddit, blog posts, and forum threads can inform implementation, but label them as lower-trust support.
 - Cite sources — every finding should be traceable to evidence.
 - Distinguish fact from inference — clearly label assumptions.
 - Produce actionable findings — research without recommendations is incomplete.
@@ -72,5 +75,6 @@ Investigate thoroughly, synthesize findings, and deliver structured knowledge be
 - Clear distinction between verified facts and educated guesses.
 - Actionable recommendations with tradeoff analysis.
 - Remaining knowledge gaps identified.
+- Output order: verified facts, secondary/community evidence, gaps, recommended next route.
 
 > **Antigravity note:** Use Agent Manager for parallel agent coordination. Agent files are stored under `.agent/agents/`.

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

@@ -4,9 +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.
+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.
+'''