AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Pick Workflow

skill-digital-stoic-org-agent-skills-pick-workflow · by digital-stoic-org

Decide HOW a skill/agent should EXECUTE — linear vs parallel fan-out, sub-agents vs dynamic Workflow, and the per-step seam — instead of defaulting to linear+single-model. Authoring-time judge: produces an execution design, does NOT run the task. Delegates the per-step model+effort call to /pick-model. Use when authoring/challenging a skill or agent, or when asked 'should this fan out', 'parallel…

No reviews yet
0 installs
38 views
0.0% view→install

Install

$ agentstack add skill-digital-stoic-org-agent-skills-pick-workflow

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-digital-stoic-org-agent-skills-pick-workflow)

Reliability & compatibility

Security review passed
0 installs to date
no reviews yet
2mo ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Pick Workflow? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Pick Workflow

Authoring-time judge for a skill/agent's execution topology. Sibling to /pick-model: it picks the model+effort for one step; this picks how steps run (linear vs fan-out, sub-agents vs Workflow, the seam) and calls /pick-model per step for the model. Emits a design — never runs the task.

When: authoring or challenging a skill/agent · deciding parallel-vs-linear · sub-agents-vs-Workflow.

Steps

1. Decompose — fill the table FIRST (it IS the analysis; no recommending before it exists)

| Step | Work shape | Parallelizable? | Judgment load | Token weight | Cross-item dep? | |---|---|---|---|---|---|

  • Work shape — read / classify / synthesize / transform / decide.
  • Parallelizable? — units independent? (per-file yes; "synthesize the whole plan" no.)
  • Judgment load — low (mechanical/schema-bound) → high (ordering, trade-offs, reversibility, intent).
  • Token weight — where cost sits (usually the step that reads everything).
  • Cross-item dep? — compares across units / needs the global graph? Correctness gate: a cross-item step must NOT be sharded. Two gates + worker rules in reference.md.

2. Cut the seam by global-context (NOT by folder/file)

Fan out per-item, judgment-light, independent work → workers return structured facts only (no dispositions/severity/decisions). Keep cross-item reasoning + dispositions + synthesis on the orchestrator. Canonical: gather (fan-out) → reason → plan (orchestrator) → execute (fan-out independent ops).

3. Pick topology + mechanism

Front-door first (Anthropic catalog in reference.md): routing (distinct input kinds → branch before fan-out) · voting / evaluator-optimizer (need confidence/refinement → run-N-vote or generate→critique→refine). Then:

| Choose | When | Gate | |---|---|---| | 🟢 Linear | Below threshold; few units — the default | simplest | | 🔵 Sub-agents (parallel) | fixed small set (2–6) independent tasks, no loop | no resume/budget | | 🟣 Workflow | fan-out over a (variable-size) list; need loop-until-dry, threshold switch, budget cap, schema extraction, verify/voting, resume | opt-in only → never a skill's default; ship a linear fallback |

Every worker needs a delegation contract: objective · output format (schema) · tool/source guidance · boundaries — else duplication/gaps.

4. Threshold, not unconditional fan-out

Fan-out has fixed cost (spawn latency, schema round-trips, orchestrator re-reads). Encode a threshold switch from the target's typical (not worst-case) input. In Workflow: one if (items < N) line.

5. Model+effort per step → call /pick-model

Do not re-derive a model table. Run /pick-model on each step's shape; write its verdict into the design. (Typical: synthesis→Opus, schema extraction→Haiku, careful transforms→Sonnet — but it decides.)

Output

  1. Step table (filled). 2. Design — seam + mechanism + threshold + per-step model. 3. Trade-offs — correctness risk avoided · conditionality · honest counter-argument for plain linear. 4. Concrete changemodel:/effort: per phase/agent(), spawns or pipeline()/parallel(), threshold, fallback.

Anti-patterns

  • ❌ "Parallel sub-agents for exploration" → shard by file → cross-item checks see a slice (the #1 trap).
  • ❌ "Cheap model for subtasks" on a judgment step → degraded dispositions/ordering.
  • ❌ Default linear+single-model unchecked — wastes tokens AND risks naive over-parallelizing.
  • ❌ Workers that judge — they extract facts; dispositions stay on the orchestrator.
  • ❌ A skill that requires Workflow — it's opt-in-gated; always ship a linear fallback.
  • ❌ Re-deriving a model table — /pick-model's job. ❌ Always-on fan-out — only above threshold.
  • ❌ Auto-running this on every SKILL.md edit — it's Opus-shaped; keep it prompt-invoked.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Versions

  • v0.1.0 Imported from the upstream source.