agents-templated 2.2.10 → 2.2.11

package/agents/commands/perf-scan.md

@@ -0,0 +1,33 @@
+# /perf-scan
+
+## A. Intent
+Measure baseline performance and detect regressions with deterministic thresholds.
+
+## B. When to Use
+Use before and after performance-sensitive changes.
+
+## C. Required Inputs
+- Baseline context
+- Target endpoints or flows
+- Performance thresholds
+
+## D. Deterministic Execution Flow
+1. Capture baseline metrics.
+2. Execute candidate workload.
+3. Compare p95/p99 latency and error rates.
+4. Flag regressions with threshold deltas.
+5. Emit optimization priorities.
+
+## E. Structured Output Template
+- `baseline_metrics`
+- `candidate_metrics`
+- `regressions[]`
+- `threshold_checks[]`
+- `recommendations[]`
+
+## F. Stop Conditions
+- Baseline missing.
+- Thresholds undefined.
+
+## G. Safety Constraints
+- Avoid performance claims without before/after evidence.

package/agents/commands/perf.md

@@ -0,0 +1,34 @@
+# /perf
+
+## A. Intent
+Evaluate and optimize performance using measurable baselines.
+
+## B. When to Use
+Use when latency, throughput, memory, or build-time regressions are reported.
+
+## C. Required Inputs
+- Target metrics
+- Baseline environment
+- Optimization scope
+
+## D. Deterministic Execution Flow
+1. Capture baseline metrics.
+2. Identify bottlenecks.
+3. Apply one optimization unit.
+4. Re-measure metrics.
+5. Compare against baseline.
+6. Emit performance report.
+
+## E. Structured Output Template
+- `baseline_metrics`
+- `optimization_units[]`
+- `post_metrics`
+- `regression_check`
+- `recommendation`
+
+## F. Stop Conditions
+- Missing baseline metrics.
+- Non-reproducible benchmark.
+
+## G. Safety Constraints
+- Do not trade security controls for performance.

package/agents/commands/plan.md

@@ -0,0 +1,34 @@
+# /plan
+
+## A. Intent
+Generate an executable implementation plan with ordered steps and risk controls.
+
+## B. When to Use
+Use for non-trivial work requiring sequencing, dependencies, and checkpoints.
+
+## C. Required Inputs
+- Objective
+- Scope boundaries
+- Constraints
+
+## D. Deterministic Execution Flow
+1. Parse objective and constraints.
+2. Extract atomic work units.
+3. Compute dependency order.
+4. Attach validation checkpoints.
+5. Attach risk and rollback notes.
+6. Emit plan artifacts.
+
+## E. Structured Output Template
+- `plan_summary`
+- `work_units[]`
+- `dependency_graph`
+- `validation_checkpoints[]`
+- `risk_register[]`
+
+## F. Stop Conditions
+- Missing objective or scope.
+- Contradictory constraints.
+
+## G. Safety Constraints
+- Include security and testing gates for code-changing units.

package/agents/commands/pr.md

@@ -0,0 +1,35 @@
+# /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.

package/agents/commands/problem-map.md

@@ -0,0 +1,33 @@
+# /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.

package/agents/commands/quality-gate.md

@@ -0,0 +1,33 @@
+# /quality-gate
+
+## A. Intent
+Enforce quality gates using test signals, behavior checks, and regression controls.
+
+## B. When to Use
+Use before release, and after major bug fixes.
+
+## C. Required Inputs
+- Target build/revision
+- Test scope
+- Critical user flows
+
+## D. Deterministic Execution Flow
+1. Run required test layers.
+2. Validate critical user flows.
+3. Inspect flaky or unstable results.
+4. Define required remediations.
+5. Emit pass/conditional/block outcome.
+
+## E. Structured Output Template
+- `test_results[]`
+- `critical_flow_status[]`
+- `quality_findings[]`
+- `required_fixes[]`
+- `gate_status`
+
+## F. Stop Conditions
+- Critical flow untested.
+- Required tests failed.
+
+## G. Safety Constraints
+- Do not mark pass when critical regressions remain open.

package/agents/commands/refactor.md

@@ -0,0 +1,34 @@
+# /refactor
+
+## A. Intent
+Improve internal structure without changing externally observable behavior.
+
+## B. When to Use
+Use for maintainability and modularity improvements.
+
+## C. Required Inputs
+- Target component/module
+- Non-functional goals
+- Behavior invariants
+
+## D. Deterministic Execution Flow
+1. Capture behavior invariants.
+2. Define refactor units.
+3. Apply one unit at a time.
+4. Verify invariants after each unit.
+5. Measure complexity delta.
+6. Emit refactor report.
+
+## E. Structured Output Template
+- `target`
+- `invariants[]`
+- `transformations[]`
+- `behavior_check_results[]`
+- `complexity_delta`
+
+## F. Stop Conditions
+- Invariant violation.
+- Missing baseline behavior.
+
+## G. Safety Constraints
+- Abort on behavior-change risk.

package/agents/commands/release-ready.md

@@ -0,0 +1,33 @@
+# /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.

package/agents/commands/release.md

@@ -0,0 +1,39 @@
+# /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.

package/agents/commands/risk-review.md

@@ -0,0 +1,33 @@
+# /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.

package/agents/commands/scaffold.md

@@ -0,0 +1,34 @@
+# /scaffold
+
+## A. Intent
+Create deterministic project/module boilerplate with secure defaults.
+
+## B. When to Use
+Use to initialize new modules/features with approved structure.
+
+## C. Required Inputs
+- Target module name
+- Runtime/stack
+- Required patterns
+
+## D. Deterministic Execution Flow
+1. Validate target path non-conflict.
+2. Resolve scaffold template.
+3. Generate file tree.
+4. Apply secure defaults.
+5. Generate baseline tests.
+6. Emit scaffold manifest.
+
+## E. Structured Output Template
+- `target`
+- `template_source`
+- `files_created[]`
+- `secure_defaults[]`
+- `tests_created[]`
+
+## F. Stop Conditions
+- Path collision.
+- Unsupported template/runtime.
+
+## G. Safety Constraints
+- Do not overwrite existing files without explicit confirmation.

package/agents/commands/scope-shape.md

@@ -0,0 +1,33 @@
+# /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.

package/agents/commands/task.md

@@ -0,0 +1,35 @@
+# /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.

package/agents/commands/test.md

@@ -0,0 +1,34 @@
+# /test
+
+## A. Intent
+Generate or execute deterministic test plans and test artifacts.
+
+## B. When to Use
+Use for feature validation, regression prevention, and release readiness.
+
+## C. Required Inputs
+- Target scope
+- Test level
+- Expected behavior
+
+## D. Deterministic Execution Flow
+1. Resolve test scope.
+2. Map behavior to test cases.
+3. Execute or generate tests.
+4. Capture pass/fail artifacts.
+5. Classify failures.
+6. Emit test report.
+
+## E. Structured Output Template
+- `scope`
+- `test_matrix[]`
+- `execution_results[]`
+- `coverage_delta`
+- `failures[]`
+
+## F. Stop Conditions
+- Unavailable runtime.
+- Undefined scope.
+
+## G. Safety Constraints
+- Do not mark success if critical tests are skipped.

package/agents/commands/ux-bar.md

@@ -0,0 +1,33 @@
+# /ux-bar
+
+## A. Intent
+Set a minimum UX quality bar with clear criteria before UI implementation.
+
+## B. When to Use
+Use when a feature has user-facing interaction or visual design impact.
+
+## C. Required Inputs
+- Target user flow
+- Existing design language
+- Accessibility requirements
+
+## D. Deterministic Execution Flow
+1. Evaluate key interaction states.
+2. Check visual hierarchy and clarity.
+3. Validate accessibility coverage.
+4. Identify UX risks and gaps.
+5. Emit UX quality checklist.
+
+## E. Structured Output Template
+- `ux_scorecard[]`
+- `interaction_states[]`
+- `accessibility_checks[]`
+- `ux_gaps[]`
+- `improvements[]`
+
+## F. Stop Conditions
+- Critical flow has undefined state handling.
+- Accessibility constraints are missing.
+
+## G. Safety Constraints
+- Preserve existing design system patterns unless an explicit redesign is approved.

package/agents/rules/planning.mdc

@@ -0,0 +1,69 @@
+---
+title: "Planning Discipline"
+description: "Every feature discussion or implementation must produce a reusable prompt plan file in .github/prompts/"
+version: "1.0.0"
+tags: ["planning", "workflow", "documentation", "prompts"]
+alwaysApply: true
+---
+
+## Purpose
+
+Ensure every feature discussion, design decision, or implementation produces a reusable prompt plan stored in `.github/prompts/`. Plans persist across sessions and serve as living context for future work — they are never discarded.
+
+## When to Apply
+
+This rule is always active. Trigger when:
+
+- User asks to implement a new feature
+- A design or architecture decision is being made
+- A significant refactor is planned
+- A bug fix requires non-trivial investigation or systemic changes
+- A discussion produces decisions that affect future work
+
+## Plan File Convention
+
+**Location:** `.github/prompts/`
+**Filename:** `YYYY-MM-DD-{feature-slug}.prompt.md`
+**Format:** VS Code reusable prompt (`.prompt.md` — usable as an `@workspace` prompt in Copilot Chat)
+
+## Required Sections
+
+Each plan file must contain:
+
+```
+---
+agent: agent
+description: One-line summary of what this plan covers.
+---
+
+## Context
+Brief background — what problem are we solving and why now.
+
+## Decision
+What we decided to do and the reasoning behind it (not just what, but why).
+
+## Steps
+Numbered implementation steps in dependency order.
+
+## Acceptance Criteria
+Concrete, testable outcomes that define "done".
+
+## Status
+- [ ] Not started  /  [ ] In progress  /  [x] Complete
+Blockers (if any):
+```
+
+## Workflow
+
+1. At the start of any feature discussion or implementation, create the plan file immediately.
+2. Use the filename convention: `YYYY-MM-DD-{feature-slug}.prompt.md`.
+3. Fill out **Context**, **Decision**, and **Steps** before starting implementation.
+4. Update **Status** and **Acceptance Criteria** incrementally as work progresses.
+5. Mark the plan complete when implementation is verified and accepted.
+
+## Guardrails
+
+- Do not skip plan creation for "small" features — small decisions accumulate into undocumented technical debt.
+- Plans are never deleted — they form a historical record of architectural decisions.
+- Plan files must not contain secrets, credentials, or PII.
+- If a plan changes significantly mid-implementation, update it in place rather than creating a new one.