agents-templated 2.2.10 → 2.2.12

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

@@ -0,0 +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

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

@@ -0,0 +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

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

package/templates/agents/commands/test.md

@@ -1,34 +1,58 @@
-# /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.
+# /test
+
+## A. Intent
+Run deterministic validation and gate release readiness based on test evidence.
+
+## B. When to Use
+- Use when validating behavior after implementation or before merge/release.
+- This command now includes quality-gate behavior; do not use /quality-gate.
+
+## C. Context Assumptions
+- Test targets are defined.
+- Required environments are available.
+- Pass/fail criteria are explicit.
+
+## D. Required Inputs
+| Input | Type | Example |
+|---------------------|------------|----------------------------------|
+| `test_scope` | string | "api regression" |
+| `test_suites` | string[] | ["unit", "integration", "critical-flow"] |
+| `evidence_artifact` | artifact | test report path or CI run URL |
+
+## E. Pre-Execution Guards <- fail fast, check ALL before running
+- [ ] test scope is non-empty
+- [ ] critical test suites are executable
+- [ ] pass criteria are declared
+
+## F. Execution Flow
+1. Collect test targets and runtime config.
+2. Execute suites in deterministic order.
+3. Aggregate results and failures.
+4. Decision point ->
+   - condition A -> critical failures present -> gate = blocked
+   - condition B ->  no critical failures -> gate = pass.
+5. Build validation evidence and remediation list.
+6. Emit test and gate report.
+
+## G. Output Schema
+
+```json
+{
+  "test_run_id": "string",
+  "results": ["array","of","strings"],
+  "gate_status": "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
+- critical test suite cannot run
+- result schema cannot be produced
+
+## J. Safety Constraints
+- Hard block: hard block when critical flow tests fail
+- Warn only: warn when flaky tests are excluded with justification

package/templates/agents/commands/ux-bar.md

@@ -0,0 +1,58 @@
+# /ux-bar
+
+## A. Intent
+Assess UX quality bar and guarantee core interaction states are defined before build.
+
+## B. When to Use
+- Use when UX quality and accessibility need pre-implementation validation.
+- Do not use as a replacement for visual design exploration.
+
+## C. Context Assumptions
+- Scope and architecture are available.
+- Primary user flows are identified.
+- Design references exist.
+
+## D. Required Inputs
+| Input | Type | Example |
+|---------------------|------------|----------------------------------|
+| `ux_goal` | string | "reduce checkout friction" |
+| `flows` | string[] | ["cart", "payment", "confirmation"] |
+| `design_artifact` | artifact | wireframes, Figma link, screenshots |
+
+## E. Pre-Execution Guards <- fail fast, check ALL before running
+- [ ] critical flows are enumerated
+- [ ] interaction states include loading/error/empty
+- [ ] accessibility checks are defined
+
+## F. Execution Flow
+1. Review flows and interaction states.
+2. Evaluate accessibility and usability risks.
+3. Score UX gaps by severity.
+4. Decision point ->
+   - condition A -> critical UX gap -> block readiness
+   - condition B ->  manageable gaps -> continue.
+5. Build prioritized improvement list.
+6. Emit UX quality package.
+
+## G. Output Schema
+
+```json
+{
+  "ux_review_id": "string",
+  "ux_gaps": ["array","of","strings"],
+  "severity": "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
+- critical flow lacks defined interaction states
+- accessibility baseline is not addressed
+
+## J. Safety Constraints
+- Hard block: hard block on unaddressed critical accessibility failures
+- Warn only: warn when medium UX issues are deferred

package/templates/agents/skills/README.md

@@ -61,12 +61,22 @@ To create a new skill for your specific domain:
 │   └── SKILL.md              # Systematic feature scoping and execution contracts
 ├── bug-triage/
 │   └── SKILL.md              # Reproduction-first debugging and regression workflows
+├── debug-skill/
+│   └── SKILL.md              # Breakpoint-first debugging and execution tracing
+├── secure-code-guardian/
+│   └── SKILL.md              # Secure-by-default coding for auth and input boundaries
+├── feature-forge/
+│   └── SKILL.md              # Requirements forging before implementation starts
 ├── error-patterns/
 │   └── SKILL.md              # Persistent debugging memory and known-fix application
 ├── app-hardening/
 │   └── SKILL.md              # Risk-based hardening and obfuscation guidance
 ├── ui-ux-pro-max/
 │   └── SKILL.md              # Premium UI/UX implementation patterns
+├── emilkowalski-skill/
+│   └── SKILL.md              # Frontend polish and animation quality checks
+├── raphaelsalaja-userinterface-wiki/
+│   └── SKILL.md              # UI hierarchy and interface best-practice playbook
 ├── my-custom-skill/
 │   └── SKILL.md              # Your custom skill
 └── README.md                 # This file
@@ -98,9 +108,14 @@ Consider creating skills for:
 
 - `feature-delivery`: Use when user asks are broad and you need objective, scope, acceptance criteria, and validation plan.
 - `bug-triage`: Use for defects and regressions requiring reproducible evidence, root-cause isolation, and minimal safe patches.
+- `debug-skill`: Use for breakpoint-driven debugging, execution tracing, and variable-state inspection.
+- `secure-code-guardian`: Use for secure-by-default implementation across auth, secrets, and untrusted input.
+- `feature-forge`: Use before coding to turn rough asks into execution-ready requirements and acceptance criteria.
 - `error-patterns`: Use when errors repeat to apply known fixes from lessons-learned and automatically record new resolutions.
 - `app-hardening`: Use for high-risk/distributed runtimes to enforce hardening profile, obfuscation decisions, and release evidence.
 - `shadcn-ui`: Use for shadcn/ui installation, component composition, form patterns, and theme customization.
+- `emilkowalski-skill`: Use for frontend animation, micro-interaction quality, and visual polish passes.
+- `raphaelsalaja-userinterface-wiki`: Use for interface hierarchy, readability, and UX consistency audits.
 
 ## Using Skills in Your Project
 

package/templates/agents/skills/debug-skill/SKILL.md

@@ -0,0 +1,39 @@
+---
+name: debug-skill
+description: Enables breakpoint-driven debugging workflows with execution tracing, state inspection, and root-cause proof before patching.
+---
+
+# Debug Skill
+
+Use this skill when the user is stuck on a bug and needs debugger-style investigation instead of print-guessing.
+
+## Trigger Conditions
+
+- User asks to debug, set breakpoints, step through code, or inspect runtime state.
+- A bug is intermittent, difficult to localize, or likely branch/state dependent.
+- Existing logs are insufficient to prove root cause.
+
+## Workflow
+
+1. Confirm a reproducible scenario and expected vs actual behavior.
+2. Define a checkpoint plan (breakpoints/log points/frames).
+3. Trace execution order across checkpoints.
+4. Capture variable-state transitions at failure boundaries.
+5. Prove root cause with execution evidence.
+6. Apply the smallest safe patch and run focused regressions.
+
+## Output Contract
+
+- Reproduction summary
+- Checkpoint plan
+- Execution trace highlights
+- State snapshots at critical steps
+- Root-cause finding
+- Minimal patch plan
+- Regression checks and residual risk
+
+## Guardrails
+
+- Do not ship speculative fixes without trace-backed evidence.
+- Do not skip regression validation after state-sensitive fixes.
+- If reproduction fails, stop and request missing runtime context.

package/templates/agents/skills/emilkowalski-skill/SKILL.md

@@ -0,0 +1,51 @@
+---
+name: emilkowalski-skill
+description: Frontend interaction and motion quality checks for polished, minimal UI.
+---
+
+# Emil Kowalski Frontend Polish
+
+Use this skill when refining frontend motion, interaction quality, and visual clarity.
+
+## Trigger Conditions
+
+- User asks to improve UI quality, animations, or perceived smoothness.
+- User wants cleaner interactions without heavy redesign.
+- Interface feels functional but not polished.
+
+## Workflow
+
+1. Baseline the current interaction quality.
+2. Remove accidental motion (janky or decorative-only animation).
+3. Define motion hierarchy: page, section, element, micro-interaction.
+4. Tune timing and easing with consistency.
+5. Validate accessibility: reduced-motion support and focus visibility.
+6. Verify mobile and desktop interaction parity.
+
+## Frontend Quality Checklist
+
+- Animation duration is intentional and consistent.
+- Entry and exit transitions communicate state changes.
+- Hover/focus/active states are visually distinct.
+- Touch targets remain accessible on mobile.
+- Layout and typography remain readable during motion.
+
+## Output Contract
+
+- Interaction problems found
+- Priority fixes (high/medium/low)
+- Motion system decisions (duration, easing, delay)
+- Accessibility checks performed
+- Before/after verification notes
+
+## Guardrails
+
+- Do not add animation where no UX value exists.
+- Prefer CSS/transform-based transitions over layout-thrashing properties.
+- Always provide a reduced-motion fallback.
+- Keep performance budget visible (FPS, input latency, layout shifts).
+
+## Upstream Reference
+
+- Original package command:
+  - npx skills add emilkowalski/skill

package/templates/agents/skills/feature-forge/SKILL.md

@@ -0,0 +1,39 @@
+---
+name: feature-forge
+description: Turns vague feature requests into execution-ready requirements, acceptance criteria, and validation plans before coding starts.
+---
+
+# Feature Forge
+
+Use this skill before implementation when feature requests are high-level, ambiguous, or under-specified.
+
+## Trigger Conditions
+
+- User says build/add/create/implement without a full spec.
+- Requirements are broad or mixed between business and technical language.
+- Scope boundaries and acceptance criteria are unclear.
+
+## Workflow
+
+1. Restate objective and target user outcome.
+2. Define in-scope and out-of-scope boundaries.
+3. Convert asks into concrete functional requirements.
+4. Produce testable acceptance criteria.
+5. Split work into dependency-ordered slices.
+6. Define validation approach and rollback notes.
+
+## Output Contract
+
+- Objective summary
+- Scope in/out
+- Functional requirements
+- Acceptance criteria
+- Implementation slices
+- Validation plan
+- Risks, assumptions, and rollback notes
+
+## Guardrails
+
+- Do not move to implementation planning without explicit scope boundaries.
+- Keep acceptance criteria measurable and testable.
+- Raise blockers when requirements conflict or remain ambiguous.