agent-afk 3.82.0 → 3.83.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -1,6 +1,7 @@
1
1
  ---
2
2
  name: contract
3
3
  description: "Reference convention for sub-agent I/O schemas. Loaded by orchestrator skills via /contract and into agents via the `skills:` field."
4
+ context: load
4
5
  ---
5
6
 
6
7
  # Contract
@@ -1,6 +1,7 @@
1
1
  ---
2
2
  name: devils-advocate
3
3
  description: "Adversarially critique a proposal by generating alternatives. Dispatches 3 parallel critics (pragmatist, paranoid, architect lenses) — each invents one alternative approach — then a synthesis step ranks all 4 options and recommends the top choice. Use when a plan, fix, scoping, decomposition, or named recommendation will drive decisions and you want structured alternative-generation before committing. Complements /shadow-verify — that skill re-derives factual claims; this one critiques whether the chosen approach itself is best."
4
+ context: load
4
5
  ---
5
6
 
6
7
  ## Sub-agent contract
@@ -2,6 +2,7 @@
2
2
  name: ground-claim
3
3
  description: "Use when the user asks a meta-capability question about a system/framework/repo ('what does X enable', 'what can this do', 'list the capabilities'). Forces file-read grounding with path:line citations before answering; tags any unverifiable claim as [UNVERIFIED]."
4
4
  argument-hint: "<the meta-capability question>"
5
+ context: load
5
6
  ---
6
7
 
7
8
  ## Trigger
@@ -1,6 +1,7 @@
1
1
  ---
2
2
  name: ground-state
3
3
  description: "Before starting any non-trivial implementation (multi-file edits, new features, config changes, anything that writes), dispatch a parallel pre-flight reconnaissance wave to triangulate git state, project infrastructure, and prior-session memory. Produces a 5-line ground-truth snapshot that grounds the implementation and catches wrong-branch edits, assumed-no-CI, stale origin, and missed memory context before the first edit."
4
+ context: fork
4
5
  ---
5
6
 
6
7
  ## Sub-agent contract
@@ -1,6 +1,7 @@
1
1
  ---
2
2
  name: intent-lock
3
3
  description: "Fires before multi-step work when the user's request contains ambiguous referents ('the text', 'her Y'), characterizations of unverified entities ('the meeting is substantive'), or identity assumptions (which contact = the user). Emits a one-sentence interpretation lock for fast async correction; escalates to Asking only when interpretation gates an irreversible action AND multiple plausible reads exist."
4
+ context: load
4
5
  ---
5
6
 
6
7
  ## When to invoke
@@ -7,6 +7,7 @@ failure_modes:
7
7
  - dependency blindness
8
8
  - false completeness
9
9
  - premature execution
10
+ context: fork
10
11
  ---
11
12
 
12
13
  ## Sub-agent contract
@@ -1,6 +1,7 @@
1
1
  ---
2
2
  name: research
3
3
  description: "Dispatches two sub-agents in parallel to gather external and local context for the current task."
4
+ context: fork
4
5
  ---
5
6
 
6
7
  ## Sub-agent contract
@@ -2,6 +2,7 @@
2
2
  name: review
3
3
  description: "Dispatches parallel dimension agents across a diff, PR (URL or number), commit SHA, branch, staged changes, or patch file — covering security, correctness, api-compat, test-coverage, and perf-observability — synthesizes findings by severity, and emits a merge recommendation. Use when changes are ready for review before merge. Read-only: this skill analyzes and reports only — it never edits files, commits, pushes, comments on a PR, or modifies the PR description."
4
4
  argument-hint: "[diff|pr-url|pr-number|commit-sha|branch|--staged|--head] [--light] [--change-type hotfix|feature|refactor|dep-bump|new-service]"
5
+ context: fork
5
6
  ---
6
7
 
7
8
  ## Read-only — hard constraint
@@ -1,6 +1,7 @@
1
1
  ---
2
2
  name: shadow-verify
3
3
  description: "Dispatch a parallel adversarial verifier wave after any high-stakes sub-agent investigation (code reviews, audits, findings reports, large refactors). Shadow verifiers independently re-derive 2–3 key claims from scratch and flag disagreements before the user acts. Use when sub-agent output will drive decisions, file changes, commits, or external side-effects."
4
+ context: fork
4
5
  ---
5
6
 
6
7
  ## Sub-agent contract
@@ -1,6 +1,7 @@
1
1
  ---
2
2
  name: ship
3
3
  description: "Release pipeline for already-done local work. Dispatches /ground-state pre-flight, runs the project test suite, drafts a commit message, pushes, and opens a PR with a structured verification summary. Use when local changes are ready to hand off to review — e.g. 'ship this', 'push and open a PR', 'release this work'. Add --verify to trigger an adversarial verifier wave on the diff before a human reads the PR."
4
+ context: fork
4
5
  ---
5
6
 
6
7
  ## Sub-agent contract
@@ -2,6 +2,7 @@
2
2
  name: simplify
3
3
  description: "Discovers incidental complexity, duplication, and dead code in a codebase and produces a ranked, behavior-preserving reduction plan — optionally applying safe changes. Dispatches four parallel read-only discovery lenses (clone detection, dead code, complexity hotspots, wrong abstraction), synthesizes into a prioritized reduction plan, and gates apply mode behind /refactor and a hard test check."
4
4
  argument-hint: "[target] [--apply] [--all]"
5
+ context: fork
5
6
  ---
6
7
 
7
8
  ## Sub-agent contract
@@ -120,4 +121,4 @@ On full success, chain to `/ship` for commit + PR.
120
121
 
121
122
  - `/refactor` — multi-site mechanical apply
122
123
  - `/ship` — commit + PR after successful apply
123
- - `/diagnose` — when an applied simplification breaks a test
124
+ - `/diagnose` — when an applied simplification breaks a test
@@ -2,6 +2,7 @@
2
2
  name: spec
3
3
  description: "Takes a loose idea and transforms it into a structured, actionable spec ready for implementation. Use when the user passes an idea, feature request, or problem description that needs scoping before building."
4
4
  argument-hint: "<idea or feature request>"
5
+ context: fork
5
6
  ---
6
7
 
7
8
  ## Triage: bugs route to /diagnose