Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 10 additions & 0 deletions .agents/skills/codex-model-routing/SKILL.md
Original file line number Diff line number Diff line change
Expand Up @@ -65,6 +65,16 @@ epic root personas are forced independently of file count.
7. Spawn the generated agent profile. Do not spawn the base alias and claim that
a different model was selected.

## Normal routed-delegation launch binding

Before every normal nested `spawn_agent` call, resolve independently for that delegation. Validate the generated profile name, model, reasoning effort, path, and SHA-256 against the resolver result and the generated profile on disk. Add
the exact validated receipt to `codex_model_routing_receipts[]`, including its non-empty `phase` and delegation identifier, in the selected checkpoint that `SubagentStart` reads. Durably flush the selected checkpoint before launch, then launch only the resolver-returned `deployment_agent`.

Reject the launch when the receipt is late, a generic alias is supplied, the
checkpoint is ambiguous, profile validation fails, persistence or durable flush
fails, or start attestation returns `routing_valid: false`. Do not accept child output or child mutations after `routing_valid: false`; retain downstream
recorder, authority-store, mutation-gate, and stop-gate enforcement.

The route name `feature-review` resolves to the native
`feature-reviewer-<profile>` agent family; retain `feature-review` as the
receipt's logical agent name.
Expand Down
2 changes: 1 addition & 1 deletion .agents/skills/epic-plan/SKILL.md
Original file line number Diff line number Diff line change
Expand Up @@ -161,7 +161,7 @@ As each preparation finishes:
3. Backfill `issue_num` and `feature_folder` in `epic.md`.
4. Record `preparation_status: "prepared"`, `research_path`, `plan_path`,
`preflight_evidence_path`, and `preflight_status: "PREFLIGHT: ALL CLEAR"` in the planner
checkpoint. `research_path` must be under `artifacts/research/` or inside the feature folder.
checkpoint. `research_path` must be under `docs/features/<feature>/research/` inside the feature folder.
Each child references its immutable receipt and the shared `wave.<wave_id>.status.json` path.
5. Remove the worktree only after its preparation branch is merged.

Expand Down
3 changes: 2 additions & 1 deletion .agents/skills/evidence-and-timestamp-conventions/SKILL.md
Original file line number Diff line number Diff line change
Expand Up @@ -31,7 +31,8 @@ The following sub-paths under `artifacts/` are FORBIDDEN for evidence output:

Allowed `artifacts/` sub-paths (non-evidence orchestration use only):
- `artifacts/orchestration/`
- `artifacts/research/`

Research output is not an `artifacts/` sub-path. Use `docs/features/<feature>/research/` for feature-associated research or `docs/research/` for one-off research.

No delegation prompt, plan task, or upstream agent instruction may override this scheme. If a caller supplies a non-canonical path, the receiving agent MUST reject it, substitute the canonical path, and record `EVIDENCE_LOCATION_OVERRIDE_REJECTED: <supplied path> replaced with <canonical path>`.

Expand Down
2 changes: 1 addition & 1 deletion .agents/skills/invoke-powershell-engineer/SKILL.md
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
---
name: invoke-powershell-engineer
description: Invoke the powershell-typed-engineer worker to design, implement, and verify PowerShell changes within typed repository boundaries. Applies PoshQC format -> analyze -> test toolchain, the 1-2 production-file direct-mode budget, the 3-production + 3-test per-batch cap, and zero-regression quality gates.
description: Invoke the powershell-typed-engineer worker to design, implement, and verify PowerShell changes within typed repository boundaries. Applies PoshQC formatting, analysis, and testing with a one-to-two production-file direct-mode budget, a three-production plus three-test batch cap, and zero-regression quality gates.
---

# Implement PowerShell Skill
Expand Down
5 changes: 3 additions & 2 deletions .agents/skills/orchestrate/SKILL.md
Original file line number Diff line number Diff line change
Expand Up @@ -284,7 +284,7 @@ After reading `artifacts/orchestration/orchestrator-state.json`, the main sessio
- `atomic-executor` — executes approved plans task-by-task
- `feature-reviewer` — produces policy, code, and feature audit artifacts by
applying the `feature-review` workflow skill
- `task-researcher` — performs deep research and writes findings to `artifacts/research/`
- `task-researcher` — performs deep research and writes findings to the applicable feature-associated `docs/features/<feature>/research/` or one-off `docs/research/` root
- `prd-feature` — produces issue, specification, and user-story artifacts when required by the selected workflow
- `staged-review` — reviews staged changes when a pre-commit review is required
- `epic-review` — reviews epic-level artifacts when the work item is an epic
Expand Down Expand Up @@ -326,14 +326,15 @@ All evidence artifacts produced during orchestration MUST comply with the canoni

Permitted `artifacts/`-rooted sub-paths (non-evidence orchestration use only):
- `artifacts/orchestration/` — orchestrator state and checkpoints
- `artifacts/research/` — research outputs from task-researcher
- `artifacts/pr_context` — PR context artifacts
- `artifacts/reviews/` — review staging artifacts
- `artifacts/status/` — status update artifacts
- `artifacts/python/` — Python coverage and lcov outputs
- `artifacts/pester/` — Pester coverage outputs
- `artifacts/csharp/` — C# coverage outputs

Research outputs from `task-researcher` are written to `docs/features/<feature>/research/` for feature-associated work or `docs/research/` for one-off work.

All other `artifacts/` sub-paths (e.g., `artifacts/baselines/`, `artifacts/qa/`, `artifacts/coverage/`, `artifacts/evidence/`) are FORBIDDEN for evidence output and will be blocked by the `enforce-evidence-locations.ps1` PreToolUse hook.

## Completion Requirements
Expand Down
2 changes: 1 addition & 1 deletion .agents/skills/powershell-change-budget-router/SKILL.md
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
---
name: powershell-change-budget-router
description: Budget-first routing contract for PowerShell work: estimate production-file scope, choose small vs large path, enforce direct-mode escalation to orchestrator, and use the VS Code extension command surface for promotion lifecycle steps when available.
description: 'Budget-first routing contract for PowerShell work: estimate production-file scope, choose small vs large path, enforce direct-mode escalation to orchestrator, and use the VS Code extension command surface for promotion lifecycle steps when available.'
---

# PowerShell Change Budget Router
Expand Down
2 changes: 1 addition & 1 deletion .agents/skills/powershell-qa-gate/SKILL.md
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
---
name: powershell-qa-gate
description: Final QA gate for PowerShell changes. Executes the full PoshQC format -> analyze -> test toolchain (with coverage where enforced), compares against a captured baseline, enforces zero-regression deltas, and produces the required reporting block before the agent declares the change complete.
description: Final QA gate for PowerShell changes. Runs PoshQC formatting, analysis, and testing with coverage where enforced; compares a captured baseline, enforces zero-regression deltas, and produces the required reporting block before completion.
---

# PowerShell QA Gate
Expand Down
4 changes: 0 additions & 4 deletions .agents/skills/powershell/SKILL.md
Original file line number Diff line number Diff line change
@@ -1,9 +1,5 @@
---
name: powershell
paths:
- "**/*.ps1"
- "**/*.psm1"
- "**/*.psd1"
description: PowerShell-specific toolchain and coding standards.
---

Expand Down
Loading
Loading