agents-templated 2.2.11 → 2.2.12

package/templates/agents/commands/pr.md

@@ -1,35 +1,58 @@
-# /pr
-
-## A. Intent
-Prepare a deterministic pull request payload with implementation evidence.
-
-## B. When to Use
-Use after validated changes are ready for review.
-
-## C. Required Inputs
-- Change summary
-- Linked issues/tasks
-- Validation evidence
-
-## D. Deterministic Execution Flow
-1. Collect changed files.
-2. Summarize intent and impact.
-3. Attach validation evidence.
-4. Classify risk and rollout impact.
-5. Build reviewer checklist.
-6. Emit PR package.
-
-## E. Structured Output Template
-- `title`
-- `summary`
-- `files_changed[]`
-- `validation_evidence[]`
-- `risk_assessment`
-- `review_checklist[]`
-
-## F. Stop Conditions
-- Missing validation evidence.
-- Open critical findings.
-
-## G. Safety Constraints
-- Block PR package when critical issues remain unresolved.
+# /pr
+
+## A. Intent
+Prepare a deterministic pull request package with implementation and validation evidence.
+
+## B. When to Use
+- Use after code changes and validation are complete and review package is needed.
+- Do not use when critical findings are still unresolved.
+
+## C. Context Assumptions
+- Change set exists.
+- Validation evidence is available.
+- Linked issue/task context is known.
+
+## D. Required Inputs
+| Input | Type | Example |
+|---------------------|------------|----------------------------------|
+| `change_summary` | string | "add retry policy to webhook worker" |
+| `linked_items` | string[] | ["ISSUE-18", "TASK-42"] |
+| `validation_evidence` | artifact | test report, benchmark output, screenshot |
+
+## E. Pre-Execution Guards <- fail fast, check ALL before running
+- [ ] change summary is complete
+- [ ] linked items are resolvable
+- [ ] validation evidence is present
+
+## F. Execution Flow
+1. Collect changed files and linked references.
+2. Summarize intent, impact, and scope.
+3. Attach validation and risk evidence.
+4. Decision point ->
+   - condition A -> critical blocker open -> abort PR package
+   - condition B ->  no blocker -> continue.
+5. Build reviewer checklist and rollout notes.
+6. Emit PR payload.
+
+## G. Output Schema
+
+```json
+{
+  "title": "string",
+  "files_changed": ["array","of","strings"],
+  "risk_assessment": "low | medium | high",
+  "blockers": "string | null"
+}
+```
+
+## H. Output Target
+- Default delivery: stdout
+- Override flag: --output=<target>
+
+## I. Stop Conditions <- abort with error message, never emit partial output
+- validation evidence missing for critical changes
+- open critical findings remain unresolved
+
+## J. Safety Constraints
+- Hard block: hard block if critical issues remain
+- Warn only: warn when non-critical follow-up items are deferred

package/templates/agents/commands/problem-map.md

@@ -1,33 +1,58 @@
-# /problem-map
-
-## A. Intent
-Define the actual user problem and measurable pain signals before solutioning.
-
-## B. When to Use
-Use at the start of an initiative when the request is a feature idea rather than a validated problem.
-
-## C. Required Inputs
-- Problem statement
-- Current user pain examples
-- Target user segment
-
-## D. Deterministic Execution Flow
-1. Extract user outcomes and friction points.
-2. Separate symptoms from root pain.
-3. Identify constraints and non-goals.
-4. Propose a focused problem frame.
-5. Emit acceptance signals for success.
-
-## E. Structured Output Template
-- `problem_frame`
-- `pain_signals[]`
-- `root_causes[]`
-- `target_user_segment`
-- `success_signals[]`
-
-## F. Stop Conditions
-- Missing target user segment.
-- No concrete pain evidence provided.
-
-## G. Safety Constraints
-- Do not lock implementation details in this stage.
+# /problem-map
+
+## A. Intent
+Frame the real user problem and guarantee a clear problem statement before planning.
+
+## B. When to Use
+- Use at the start of a feature cycle when pain points are unclear or broad.
+- Do not use for implementation details or code-level debugging.
+
+## C. Context Assumptions
+- User objective is available.
+- Stakeholder context can be collected.
+- Outcome can be stated as a measurable problem.
+
+## D. Required Inputs
+| Input | Type | Example |
+|---------------------|------------|----------------------------------|
+| `user_problem` | string | "onboarding drop-off at step 2" |
+| `signals` | string[] | ["support tickets", "analytics"] |
+| `evidence_artifact` | artifact | funnel screenshot, issue links |
+
+## E. Pre-Execution Guards <- fail fast, check ALL before running
+- [ ] problem statement is concrete
+- [ ] signals support the stated pain
+- [ ] scope remains problem-focused
+
+## F. Execution Flow
+1. Collect user pain signals and context.
+2. Synthesize candidate problem statements.
+3. Validate statement against evidence.
+4. Decision point ->
+   - condition A -> weak evidence -> request stronger signals
+   - condition B ->  strong evidence -> continue.
+5. Produce framed problem and success criteria.
+6. Emit problem map package.
+
+## G. Output Schema
+
+```json
+{
+  "problem_id": "string",
+  "core_pains": ["array","of","strings"],
+  "urgency": "low | medium | high",
+  "unknowns": "string | null"
+}
+```
+
+## H. Output Target
+- Default delivery: stdout
+- Override flag: --output=<target>
+
+## I. Stop Conditions <- abort with error message, never emit partial output
+- problem statement remains vague
+- evidence contradicts proposed framing
+
+## J. Safety Constraints
+- Hard block: hard block on fabricated assumptions presented as facts
+- Warn only: warn when evidence quality is limited

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

@@ -1,33 +1,58 @@
-# /release-ready
-
-## A. Intent
-Validate release readiness with checks for quality, risk, and rollback.
-
-## B. When to Use
-Use immediately before opening or merging a release PR.
-
-## C. Required Inputs
-- Change summary
-- Validation evidence
-- Deployment path
-
-## D. Deterministic Execution Flow
-1. Confirm test and quality gate outcomes.
-2. Confirm risk-review status.
-3. Verify migration and deploy prerequisites.
-4. Verify rollback plan.
-5. Emit release readiness decision.
-
-## E. Structured Output Template
-- `release_scope`
-- `checks_passed[]`
-- `blocking_issues[]`
-- `rollback_plan`
-- `ready_status`
-
-## F. Stop Conditions
-- Blocking issue unresolved.
-- Rollback plan absent.
-
-## G. Safety Constraints
-- Do not approve release when required evidence is missing.
+# /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,39 +1,58 @@
-# /release
-
-## A. Intent
-Produce deterministic release readiness decision and rollout contract.
-
-## B. When to Use
-Use when promoting validated changes to release channels.
-
-## C. Required Inputs
-- Version/tag
-- Change manifest
-- Rollback strategy
-- Hardening verification evidence (when required by risk profile)
-
-## D. Deterministic Execution Flow
-1. Validate release prerequisites.
-2. Validate compatibility and migration risks.
-3. Validate security and test gates.
-4. Validate hardening verification evidence when hardening-required profile applies.
-5. Build release notes.
-6. Build rollout and rollback steps.
-7. Emit release contract.
-
-## E. Structured Output Template
-- `version`
-- `release_readiness`
-- `gates[]`
-- `rollout_plan[]`
-- `rollback_plan[]`
-- `release_notes`
-- `hardening_verification`
-
-## F. Stop Conditions
-- Gate failure.
-- Missing rollback strategy.
-
-## G. Safety Constraints
-- Block release when any critical gate fails.
-- Block release when required hardening evidence is missing.
+# /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,33 +1,58 @@
-# /risk-review
-
-## A. Intent
-Identify release risks that may pass CI but fail in production.
-
-## B. When to Use
-Use before merge or release candidate approval.
-
-## C. Required Inputs
-- Proposed changes
-- Test and validation status
-- Deployment context
-
-## D. Deterministic Execution Flow
-1. Inspect behavior deltas.
-2. Rank risks by impact and likelihood.
-3. Validate mitigation or rollback paths.
-4. Identify missing tests.
-5. Emit ship recommendation.
-
-## E. Structured Output Template
-- `risk_findings[]`
-- `severity_summary`
-- `mitigations[]`
-- `rollback_readiness`
-- `release_recommendation`
-
-## F. Stop Conditions
-- High-severity risk has no mitigation.
-- Rollback path is undefined.
-
-## G. Safety Constraints
-- Block release for unresolved high-severity findings.
+# /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,33 +1,58 @@
-# /scope-shape
-
-## A. Intent
-Constrain scope to the smallest high-leverage release that still proves value.
-
-## B. When to Use
-Use after problem framing and before architecture planning.
-
-## C. Required Inputs
-- Problem frame
-- Candidate feature list
-- Delivery constraints
-
-## D. Deterministic Execution Flow
-1. Rank features by impact and effort.
-2. Define must-have vs defer list.
-3. Freeze first-release boundaries.
-4. Add explicit out-of-scope items.
-5. Emit scope decision rationale.
-
-## E. Structured Output Template
-- `scope_in[]`
-- `scope_out[]`
-- `tradeoffs[]`
-- `release_goal`
-- `defer_queue[]`
-
-## F. Stop Conditions
-- Scope still exceeds constraints.
-- No out-of-scope list produced.
-
-## G. Safety Constraints
-- Prefer one reversible release over broad irreversible scope.
+# /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,35 +1,58 @@
-# /task
-
-## A. Intent
-Convert a plan item into a deterministic execution task.
-
-## B. When to Use
-Use for bounded work with clear acceptance criteria.
-
-## C. Required Inputs
-- Task identifier
-- Acceptance criteria
-- Allowed scope
-
-## D. Deterministic Execution Flow
-1. Resolve task identifier.
-2. Validate acceptance criteria completeness.
-3. Validate scope boundaries.
-4. Define execution steps.
-5. Define verification steps.
-6. Emit task contract.
-
-## E. Structured Output Template
-- `task_id`
-- `objective`
-- `allowed_scope`
-- `execution_steps[]`
-- `verification_steps[]`
-- `acceptance_criteria[]`
-
-## F. Stop Conditions
-- Unknown task identifier.
-- Missing acceptance criteria.
-
-## G. Safety Constraints
-- Reject out-of-scope changes.
+# /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