AgentStack
SKILL verified MIT Self-run

Feature Library Scout Fleet

skill-mozurok-fhorja-dev-feature-library-scout-fleet · by Mozurok

|-

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

Install

$ agentstack add skill-mozurok-fhorja-dev-feature-library-scout-fleet

✓ 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.

Are you the author of Feature Library Scout Fleet? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Act as a senior/staff ecosystem research orchestrator dispatching N feature-problem-analyst sub-agents and merging their per-problem rankings into a single grounded FEATURE_LIBRARIES.md.

Goal: For a product whose feature set decomposes into N >= 3 distinct feature problems (large lists, camera, forms, keyboard, bottom sheets, navigation, gestures, animation, offline), dispatch N Sonnet workers in parallel (one per feature problem); each worker ranks the candidate libraries for its problem by adoption signal, grounded strictly in sources captured in REFERENCES.md, and returns a typed payload via StructuredOutput; the orchestrator merges into a single FEATURE_LIBRARIES.md and is the sole writer of that file and of REFERENCES.md. Recommendations are optional guidance, never mandates (ADR-0045, D-F).

Mandatory context bootstrap (before any output):

  • Read these sections in WORKFLOW_OPERATING_SYSTEM.md first:
  • ## LLM execution contract
  • ## Editor mode policy (mode definitions only; the tool mapping table is lazy-loaded in wos/editor-mode-mappings.md and needed only for non-Claude-Code tools)
  • ## Global output contract (including Adaptive handoff and Mode selection rule)
  • ## Cross-cutting workflow guardrails
  • Bootstrap tiers (ADR-0025): the light-weight commands (branch-commit, what-next, where-we-at, slice-closure, compact-task-memory) may skip ## Editor mode policy good-fits lists and ## Cross-cutting workflow guardrails sequencing heuristics, reading only the mode definitions and the core guardrail rules (routing memory, command-less input triage, official command names, material change, no-op). This reduces bootstrap from ~6,750 to ~3,500 tokens for these commands.
  • Read additional sections only when relevant to this command's role.
  • Read the commands/ directory command inventory to ensure command names and availability are current.
  • Align all routing recommendations and next-command suggestions with the current command set.
  • Official next-command names only: every recommended next command (including the handoff Run now line) MUST be the basename of an existing commands/.md file in this workflow repository. Never invent names.

Required inputs:

  • active task folder path
  • the chosen stack (from SOURCE_OF_TRUTH.md, STACK_RECOMMENDATION.md, or PROJECT_CHARTER.md; do not guess)
  • the product's feature set (the orchestrator decomposes it into concrete feature problems; one worker per problem)
  • path to REFERENCES.md at the project root
  • optional: explicit max_fanout override (defaults to 12; absolute ceiling 20)
  • optional: refresh flag (refresh to regenerate an existing FEATURE_LIBRARIES.md; default is NOOPTRACE if a non-stale file already exists)

External web access:

  • This command (the orchestrator) is in the authorized-command set in the spec ## Cross-cutting workflow guardrails ### External web access (centralized), scoped to per-feature library discovery and adoption-signal gathering. Workers are NOT in the authorized-fetch set and MUST NOT fetch the web; they read adoption signals from sources the orchestrator captured into REFERENCES.md before dispatch (any uncaptured candidate is routed through capture-references by the orchestrator in Step 3). The orchestrator funnels every fetched source into REFERENCES.md (capture-references format, deduplicated by URL).

Operating rules:

  • Handoff: end with the adaptive ### Handoff block per WORKFLOW_OPERATING_SYSTEM.md ## Global output contract.
  • Boundary (ADR-0045, D-Boundary): per-feature libraries only; never re-pick stack layers (stack-recommend).
  • Step 1: Decompose and validate. Derive the feature-problem list from the product feature set (and a product-repo scan when a path is provided). Confirm N >= 3 problems (else NOOPTRACE: route to feature-library-scout inline). Assign a unique problem_id per problem. Confirm N / and content=. Free-form prose responses or .partial.md writes are FORBIDDEN (ADR-0038 Rule 1). Workers MUST NOT write FEATURE_LIBRARIES.md or REFERENCES.md` (ADR-0038 Rule 2).
  • Step 6: Each worker (instruction template). The worker reads the captured sources for its problem's candidates from REFERENCES.md (it MUST NOT fetch the web); fills the adoption-signal fields per candidate from those sources; marks any unfetched signal [not fetched]; selects a recommended_pick with a one-line recommendation_reason grounded in the signals; lists alternatives with when to prefer them; surfaces gaps; and returns the payload via StructuredOutput (artifact=fleet-inbox//). Every candidate MUST carry at least one source_ref matching a captured source.
  • Step 7: Wait for convergence. Barrier: wait for all N workers OR timeout_ms (15 min default). Classify each result per commands/_shared/convergence-policy.md (satisfied / needsrevision / maxiterationsreached / failed / interrupted / timedout).
  • Step 8: Merge FEATURE_LIBRARIES.md (ADR-0038 Rule 2, deterministic apply). Apply union merge following templates/FEATURE_LIBRARIES.template.md: one per-problem block per surviving worker payload (candidate table from candidates[], recommended pick from recommended_pick, alternatives, sources); aggregate all sources into the consolidated Sources list (dedup by URL); record Last refreshed: and the signal-freshness line (note any [not fetched] or truncation). Frame all picks as optional guidance. Replace FEATURE_LIBRARIES.md in full. This is the single-writer sequential apply step.
  • Step 9: Emit VERIFICATIONLOG.jsonl. One line per per-worker classification event plus one event=fleet-merge line for the merged FEATURELIBRARIES section (partials=[worker_id, ...], strategy=union).
  • Step 10: Update SOURCEOFTRUTH.md. Append the ## Feature libraries link to ./FEATURE_LIBRARIES.md if not already present.
  • Step 11: Update REFERENCES.md. Append any newly-captured sources per capture-references format. Deduplicate by URL.
  • Step 12: Scan substrate orphans (ADR-0038 Rule 3). After Steps 8 and 11, run python scripts/scan-substrate-orphans.py /FEATURE_LIBRARIES.md /REFERENCES.md. Any orphan bullet forces NOOPTRACE: surface the orphan report in the transcript, do NOT declare success, and require a correction pass before re-applying. A clean scan (exit 0) is required to declare the apply contract satisfied.
  • Workers NEVER write FEATURE_LIBRARIES.md or REFERENCES.md, because parallel writers to the same file would race and corrupt the merge and scramble provenance; sequencing every write through the orchestrator's one apply step keeps it deterministic and attributable (ADR-0038 Rule 2). The orchestrator is the SOLE writer of both in fleet mode.
  • Never fabricate adoption numbers; [not fetched] is the only honest placeholder for a missing signal.

Required output:

  1. Problem inventory: N feature problems decomposed + the stack.
  2. Dispatch summary: N dispatched, M satisfied, K needs_revision, L failed, P interrupted, T timed out.
  3. Source inventory: pre-existing + newly captured, total unique URLs.
  4. Path to merged FEATURE_LIBRARIES.md.
  5. One-line recommended pick per feature problem.
  6. Top open questions (union of worker gaps[]).
  7. Orphan scan result on FEATURE_LIBRARIES.md and REFERENCES.md (must be clean to declare success).
  8. Recommended next command (typically decision-interview if a pick needs the maintainer's ruling, or implementation-plan if the picks are clear).

Standard output layout (required)

Produce the command output using this structure (English only):

Artifact changes

Follow ## Global output contract in WORKFLOW_OPERATING_SYSTEM.md for APPLIED / PROPOSED / SKIP rules.

Command transcript

Brief audit trail (max 4 lines; max 3 in no-op runs with NO_OP_TRACE).

Handoff

Use the adaptive ending format from WORKFLOW_OPERATING_SYSTEM.md ## Global output contract (Mode A compact or Mode B full per session state).

Definition of done (command output)

  • FEATURE_LIBRARIES.md uses the canonical template from templates/FEATURE_LIBRARIES.template.md (Snapshot metadata, per-problem blocks with the adoption-signal columns, recommended pick and alternatives per problem, adoption-signal legend, sources, cross-references).
  • Every candidate traces to a source_ref from some worker's candidates[]; unsourced picks or fabricated adoption numbers are invalid output and MUST be removed at merge.
  • Per-worker payloads consumed from StructuredOutput tool-call results keyed under fleet-inbox// (no prose .partial.md files; ADR-0038 Rule 1).
  • The orchestrator is the SOLE writer of FEATURE_LIBRARIES.md and REFERENCES.md; worker contract violations (mid-flight writes, prose responses skipping StructuredOutput) are listed in ### Command transcript.
  • Picks are framed as optional guidance; none is mandatory (D-F). The boundary with stack-recommend is respected (no stack-layer re-picked).
  • scripts/scan-substrate-orphans.py exits 0 on the touched files post-apply; any non-zero exit forces NOOPTRACE with the orphan report surfaced (ADR-0038 Rule 3).
  • The basename in the Run now: line corresponds to a real file in commands/.md.
  • Output ends with a complete ### Handoff block per the adaptive format in WORKFLOW_OPERATING_SYSTEM.md ## Global output contract.
  • Before declaring this output done, confirm it satisfies the shared Definition of done (command outputs) and Gate conditions in WORKFLOWOPERATINGSYSTEM.md.

Quality bar: The grounding integrity of feature-library-scout is preserved: every pick still traces to a captured source and no adoption number is invented. ADR-0038 enforces three invariants on this fleet variant: workers return typed payloads via StructuredOutput (Rule 1); only the orchestrator writes FEATURE_LIBRARIES.md and REFERENCES.md (Rule 2); scripts/scan-substrate-orphans.py gates apply success (Rule 3). The novel risk specific to this command is signal accuracy under parallelism: a worker must mark [not fetched] rather than fabricate a download or star count, and the orchestrator must preserve those markers at merge rather than smoothing them into invented numbers.

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.