agents-templated 2.2.18 → 2.2.20

package/templates/agents/commands/release-ready.md

@@ -1,58 +1,58 @@
-# /release-ready
-
-## A. Intent
-Validate pre-release readiness gates and guarantee deploy prerequisites are satisfied.
-
-## B. When to Use
-- Use after implementation/tests/risk review and before final release decision.
-- Do not use to execute deployment itself.
-
-## C. Context Assumptions
-- Release candidate exists.
-- All required gate outputs are available.
-- Rollout and rollback plans are drafted.
-
-## D. Required Inputs
-| Input | Type | Example |
-|---------------------|------------|----------------------------------|
-| `candidate_version` | string | "v2.4.0-rc1" |
-| `gate_artifacts` | string[] | ["test", "risk-review", "perf-scan"] |
-| `release_artifact` | artifact | release checklist, migration plan |
-
-## E. Pre-Execution Guards <- fail fast, check ALL before running
-- [ ] mandatory gates are present
-- [ ] critical blockers are resolved
-- [ ] rollback steps are executable
-
-## F. Execution Flow
-1. Collect gate evidence for candidate.
-2. Validate checklist completion.
-3. Verify rollout and rollback readiness.
-4. Decision point ->
-   - condition A -> missing mandatory gate -> block readiness
-   - condition B ->  all gates complete -> continue.
-5. Assemble readiness summary and open items.
-6. Emit release-ready report.
-
-## G. Output Schema
-
-```json
-{
-  "readiness_id": "string",
-  "gate_status": ["array","of","strings"],
-  "readiness_risk": "low | medium | high",
-  "blocker": "string | null"
-}
-```
-
-## H. Output Target
-- Default delivery: stdout
-- Override flag: --output=<target>
-
-## I. Stop Conditions <- abort with error message, never emit partial output
-- mandatory gate missing or failed
-- rollback execution path is unverified
-
-## J. Safety Constraints
-- Hard block: hard block when release checklist is incomplete on critical items
-- Warn only: warn when non-critical items are deferred
+# /release-ready
+
+## A. Intent
+Validate pre-release readiness gates and guarantee deploy prerequisites are satisfied.
+
+## B. When to Use
+- Use after implementation/tests/risk review and before final release decision.
+- Do not use to execute deployment itself.
+
+## C. Context Assumptions
+- Release candidate exists.
+- All required gate outputs are available.
+- Rollout and rollback plans are drafted.
+
+## D. Required Inputs
+| Input | Type | Example |
+|---------------------|------------|----------------------------------|
+| `candidate_version` | string | "v2.4.0-rc1" |
+| `gate_artifacts` | string[] | ["test", "risk-review", "perf-scan"] |
+| `release_artifact` | artifact | release checklist, migration plan |
+
+## E. Pre-Execution Guards <- fail fast, check ALL before running
+- [ ] mandatory gates are present
+- [ ] critical blockers are resolved
+- [ ] rollback steps are executable
+
+## F. Execution Flow
+1. Collect gate evidence for candidate.
+2. Validate checklist completion.
+3. Verify rollout and rollback readiness.
+4. Decision point ->
+   - condition A -> missing mandatory gate -> block readiness
+   - condition B ->  all gates complete -> continue.
+5. Assemble readiness summary and open items.
+6. Emit release-ready report.
+
+## G. Output Schema
+
+```json
+{
+  "readiness_id": "string",
+  "gate_status": ["array","of","strings"],
+  "readiness_risk": "low | medium | high",
+  "blocker": "string | null"
+}
+```
+
+## H. Output Target
+- Default delivery: stdout
+- Override flag: --output=<target>
+
+## I. Stop Conditions <- abort with error message, never emit partial output
+- mandatory gate missing or failed
+- rollback execution path is unverified
+
+## J. Safety Constraints
+- Hard block: hard block when release checklist is incomplete on critical items
+- Warn only: warn when non-critical items are deferred

package/templates/agents/commands/release.md

@@ -1,58 +1,58 @@
-# /release
-
-## A. Intent
-Generate deterministic release decision package with rollout and rollback readiness.
-
-## B. When to Use
-- Use when deciding whether to ship to production.
-- Do not use before release-ready checks are complete.
-
-## C. Context Assumptions
-- Release candidate is identified.
-- Pre-release checks are completed.
-- Rollback strategy is defined.
-
-## D. Required Inputs
-| Input | Type | Example |
-|---------------------|------------|----------------------------------|
-| `version` | string | "v2.4.0" |
-| `gate_results` | string[] | ["tests-pass", "risk-review-pass"] |
-| `release_artifacts` | artifact | release notes draft, migration plan |
-
-## E. Pre-Execution Guards <- fail fast, check ALL before running
-- [ ] version is valid and unique
-- [ ] required gates are complete
-- [ ] rollback plan exists
-
-## F. Execution Flow
-1. Collect gate outputs and release artifacts.
-2. Validate rollout and rollback prerequisites.
-3. Classify release risk.
-4. Decision point ->
-   - condition A -> high unresolved risk -> block release
-   - condition B ->  acceptable risk -> continue.
-5. Build release decision and communication payload.
-6. Emit release package.
-
-## G. Output Schema
-
-```json
-{
-  "release_id": "string",
-  "gates": ["array","of","strings"],
-  "release_risk": "low | medium | high",
-  "rollback_status": "string | null"
-}
-```
-
-## H. Output Target
-- Default delivery: stdout
-- Override flag: --output=<target>
-
-## I. Stop Conditions <- abort with error message, never emit partial output
-- required gate missing or failed
-- rollback plan is undefined
-
-## J. Safety Constraints
-- Hard block: hard block on unresolved high-severity release risks
-- Warn only: warn when rollout is phased due to uncertainty
+# /release
+
+## A. Intent
+Generate deterministic release decision package with rollout and rollback readiness.
+
+## B. When to Use
+- Use when deciding whether to ship to production.
+- Do not use before release-ready checks are complete.
+
+## C. Context Assumptions
+- Release candidate is identified.
+- Pre-release checks are completed.
+- Rollback strategy is defined.
+
+## D. Required Inputs
+| Input | Type | Example |
+|---------------------|------------|----------------------------------|
+| `version` | string | "v2.4.0" |
+| `gate_results` | string[] | ["tests-pass", "risk-review-pass"] |
+| `release_artifacts` | artifact | release notes draft, migration plan |
+
+## E. Pre-Execution Guards <- fail fast, check ALL before running
+- [ ] version is valid and unique
+- [ ] required gates are complete
+- [ ] rollback plan exists
+
+## F. Execution Flow
+1. Collect gate outputs and release artifacts.
+2. Validate rollout and rollback prerequisites.
+3. Classify release risk.
+4. Decision point ->
+   - condition A -> high unresolved risk -> block release
+   - condition B ->  acceptable risk -> continue.
+5. Build release decision and communication payload.
+6. Emit release package.
+
+## G. Output Schema
+
+```json
+{
+  "release_id": "string",
+  "gates": ["array","of","strings"],
+  "release_risk": "low | medium | high",
+  "rollback_status": "string | null"
+}
+```
+
+## H. Output Target
+- Default delivery: stdout
+- Override flag: --output=<target>
+
+## I. Stop Conditions <- abort with error message, never emit partial output
+- required gate missing or failed
+- rollback plan is undefined
+
+## J. Safety Constraints
+- Hard block: hard block on unresolved high-severity release risks
+- Warn only: warn when rollout is phased due to uncertainty

package/templates/agents/commands/risk-review.md

@@ -1,58 +1,58 @@
-# /risk-review
-
-## A. Intent
-Perform deterministic release risk review with mitigation and rollback readiness.
-
-## B. When to Use
-- Use before merge or release approval on non-trivial changes.
-- Do not use as a substitute for running tests.
-
-## C. Context Assumptions
-- Change set is available.
-- Validation evidence exists.
-- Deployment context is known.
-
-## D. Required Inputs
-| Input | Type | Example |
-|---------------------|------------|----------------------------------|
-| `change_set` | string | "payment retry + queue changes" |
-| `validation_status` | string[] | ["unit pass", "integration pass"] |
-| `deployment_artifact` | artifact | rollout plan, env config snapshot |
-
-## E. Pre-Execution Guards <- fail fast, check ALL before running
-- [ ] change set is fully described
-- [ ] validation status is current
-- [ ] rollback path is defined
-
-## F. Execution Flow
-1. Inspect behavior deltas and blast radius.
-2. Rank risks by impact and likelihood.
-3. Validate mitigations and rollback readiness.
-4. Decision point ->
-   - condition A -> high unresolved risk -> block recommendation
-   - condition B ->  acceptable risk -> continue.
-5. Build release risk summary and actions.
-6. Emit risk review report.
-
-## G. Output Schema
-
-```json
-{
-  "review_id": "string",
-  "risks": ["array","of","strings"],
-  "risk_level": "low | medium | high",
-  "recommendation": "string | null"
-}
-```
-
-## H. Output Target
-- Default delivery: stdout
-- Override flag: --output=<target>
-
-## I. Stop Conditions <- abort with error message, never emit partial output
-- high-severity risk has no mitigation
-- rollback readiness is undefined
-
-## J. Safety Constraints
-- Hard block: hard block on unresolved high-severity risks
-- Warn only: warn when medium risks are accepted with owner
+# /risk-review
+
+## A. Intent
+Perform deterministic release risk review with mitigation and rollback readiness.
+
+## B. When to Use
+- Use before merge or release approval on non-trivial changes.
+- Do not use as a substitute for running tests.
+
+## C. Context Assumptions
+- Change set is available.
+- Validation evidence exists.
+- Deployment context is known.
+
+## D. Required Inputs
+| Input | Type | Example |
+|---------------------|------------|----------------------------------|
+| `change_set` | string | "payment retry + queue changes" |
+| `validation_status` | string[] | ["unit pass", "integration pass"] |
+| `deployment_artifact` | artifact | rollout plan, env config snapshot |
+
+## E. Pre-Execution Guards <- fail fast, check ALL before running
+- [ ] change set is fully described
+- [ ] validation status is current
+- [ ] rollback path is defined
+
+## F. Execution Flow
+1. Inspect behavior deltas and blast radius.
+2. Rank risks by impact and likelihood.
+3. Validate mitigations and rollback readiness.
+4. Decision point ->
+   - condition A -> high unresolved risk -> block recommendation
+   - condition B ->  acceptable risk -> continue.
+5. Build release risk summary and actions.
+6. Emit risk review report.
+
+## G. Output Schema
+
+```json
+{
+  "review_id": "string",
+  "risks": ["array","of","strings"],
+  "risk_level": "low | medium | high",
+  "recommendation": "string | null"
+}
+```
+
+## H. Output Target
+- Default delivery: stdout
+- Override flag: --output=<target>
+
+## I. Stop Conditions <- abort with error message, never emit partial output
+- high-severity risk has no mitigation
+- rollback readiness is undefined
+
+## J. Safety Constraints
+- Hard block: hard block on unresolved high-severity risks
+- Warn only: warn when medium risks are accepted with owner

package/templates/agents/commands/scope-shape.md

@@ -1,58 +1,58 @@
-# /scope-shape
-
-## A. Intent
-Constrain delivery scope to the smallest high-value reversible release.
-
-## B. When to Use
-- Use after problem framing and before architectural design.
-- Do not use when requirements are already contractually frozen.
-
-## C. Context Assumptions
-- Problem map exists.
-- Candidate feature list exists.
-- Delivery constraints are known.
-
-## D. Required Inputs
-| Input | Type | Example |
-|---------------------|------------|----------------------------------|
-| `scope_goal` | string | "ship MVP in 2 weeks" |
-| `candidate_items` | string[] | ["email login", "social login", "tutorial"] |
-| `constraint_artifact` | artifact | timeline doc, staffing snapshot |
-
-## E. Pre-Execution Guards <- fail fast, check ALL before running
-- [ ] scope goal is explicit
-- [ ] candidate items are ranked
-- [ ] out-of-scope list can be produced
-
-## F. Execution Flow
-1. Rank candidate items by value and effort.
-2. Draft in-scope and out-of-scope sets.
-3. Check scope against constraints.
-4. Decision point ->
-   - condition A -> scope exceeds constraints -> trim to MVP
-   - condition B ->  feasible scope -> continue.
-5. Build scope rationale and tradeoffs.
-6. Emit scope decision package.
-
-## G. Output Schema
-
-```json
-{
-  "scope_id": "string",
-  "scope_in": ["array","of","strings"],
-  "confidence": "low | medium | high",
-  "scope_out": "string | null"
-}
-```
-
-## H. Output Target
-- Default delivery: stdout
-- Override flag: --output=<target>
-
-## I. Stop Conditions <- abort with error message, never emit partial output
-- scope cannot satisfy constraints
-- no explicit out-of-scope definition is produced
-
-## J. Safety Constraints
-- Hard block: hard block on hidden scope creep
-- Warn only: warn when deferred items carry significant risk
+# /scope-shape
+
+## A. Intent
+Constrain delivery scope to the smallest high-value reversible release.
+
+## B. When to Use
+- Use after problem framing and before architectural design.
+- Do not use when requirements are already contractually frozen.
+
+## C. Context Assumptions
+- Problem map exists.
+- Candidate feature list exists.
+- Delivery constraints are known.
+
+## D. Required Inputs
+| Input | Type | Example |
+|---------------------|------------|----------------------------------|
+| `scope_goal` | string | "ship MVP in 2 weeks" |
+| `candidate_items` | string[] | ["email login", "social login", "tutorial"] |
+| `constraint_artifact` | artifact | timeline doc, staffing snapshot |
+
+## E. Pre-Execution Guards <- fail fast, check ALL before running
+- [ ] scope goal is explicit
+- [ ] candidate items are ranked
+- [ ] out-of-scope list can be produced
+
+## F. Execution Flow
+1. Rank candidate items by value and effort.
+2. Draft in-scope and out-of-scope sets.
+3. Check scope against constraints.
+4. Decision point ->
+   - condition A -> scope exceeds constraints -> trim to MVP
+   - condition B ->  feasible scope -> continue.
+5. Build scope rationale and tradeoffs.
+6. Emit scope decision package.
+
+## G. Output Schema
+
+```json
+{
+  "scope_id": "string",
+  "scope_in": ["array","of","strings"],
+  "confidence": "low | medium | high",
+  "scope_out": "string | null"
+}
+```
+
+## H. Output Target
+- Default delivery: stdout
+- Override flag: --output=<target>
+
+## I. Stop Conditions <- abort with error message, never emit partial output
+- scope cannot satisfy constraints
+- no explicit out-of-scope definition is produced
+
+## J. Safety Constraints
+- Hard block: hard block on hidden scope creep
+- Warn only: warn when deferred items carry significant risk

package/templates/agents/commands/task.md

@@ -1,58 +1,58 @@
-# /task
-
-## A. Intent
-Convert approved plans into deterministic, execution-ready task batches.
-
-## B. When to Use
-- Use when a plan exists and work must be distributed to implementers.
-- Do not use before planning is complete.
-
-## C. Context Assumptions
-- An approved plan exists.
-- Owners and execution context are known.
-- Dependencies can be sequenced.
-
-## D. Required Inputs
-| Input | Type | Example |
-|---------------------|------------|----------------------------------|
-| `plan_id` | string | "plan-2026-04-03" |
-| `task_scope` | string[] | ["api", "ui", "tests"] |
-| `source_artifacts` | artifact | plan file path or issue board URL |
-
-## E. Pre-Execution Guards <- fail fast, check ALL before running
-- [ ] plan exists and is approved
-- [ ] task scope maps to explicit plan items
-- [ ] dependency order is resolvable
-
-## F. Execution Flow
-1. Read plan outputs and dependency graph.
-2. Split work into atomic tasks.
-3. Assign execution order and ownership metadata.
-4. Decision point ->
-   - condition A -> blocking dependency found -> move item to blocked queue
-   - condition B ->  no blockers -> keep in active queue.
-5. Build task package with acceptance checks.
-6. Emit task list and execution order.
-
-## G. Output Schema
-
-```json
-{
-  "task_batch_id": "string",
-  "tasks": ["array","of","strings"],
-  "priority": "low | medium | high",
-  "blocker": "string | null"
-}
-```
-
-## H. Output Target
-- Default delivery: stdout
-- Override flag: --output=<target>
-
-## I. Stop Conditions <- abort with error message, never emit partial output
-- plan_id is missing or invalid
-- critical dependency cannot be resolved
-
-## J. Safety Constraints
-- Hard block: no task emission without traceability to a plan item
-- Warn only: warn when owner assignment is temporary
+# /task
+
+## A. Intent
+Convert approved plans into deterministic, execution-ready task batches.
+
+## B. When to Use
+- Use when a plan exists and work must be distributed to implementers.
+- Do not use before planning is complete.
+
+## C. Context Assumptions
+- An approved plan exists.
+- Owners and execution context are known.
+- Dependencies can be sequenced.
+
+## D. Required Inputs
+| Input | Type | Example |
+|---------------------|------------|----------------------------------|
+| `plan_id` | string | "plan-2026-04-03" |
+| `task_scope` | string[] | ["api", "ui", "tests"] |
+| `source_artifacts` | artifact | plan file path or issue board URL |
+
+## E. Pre-Execution Guards <- fail fast, check ALL before running
+- [ ] plan exists and is approved
+- [ ] task scope maps to explicit plan items
+- [ ] dependency order is resolvable
+
+## F. Execution Flow
+1. Read plan outputs and dependency graph.
+2. Split work into atomic tasks.
+3. Assign execution order and ownership metadata.
+4. Decision point ->
+   - condition A -> blocking dependency found -> move item to blocked queue
+   - condition B ->  no blockers -> keep in active queue.
+5. Build task package with acceptance checks.
+6. Emit task list and execution order.
+
+## G. Output Schema
+
+```json
+{
+  "task_batch_id": "string",
+  "tasks": ["array","of","strings"],
+  "priority": "low | medium | high",
+  "blocker": "string | null"
+}
+```
+
+## H. Output Target
+- Default delivery: stdout
+- Override flag: --output=<target>
+
+## I. Stop Conditions <- abort with error message, never emit partial output
+- plan_id is missing or invalid
+- critical dependency cannot be resolved
+
+## J. Safety Constraints
+- Hard block: no task emission without traceability to a plan item
+- Warn only: warn when owner assignment is temporary