lvlup-sw/exarchos

discover

Research and discovery workflow for document deliverables — competitive analyses, architecture comparisons, ADR scaffolding, literature reviews, vendor evaluations.

Voir la source

Mode d’emploi

  1. Copiez la commande et examinez le paquet avant de l’installer dans votre environnement agent.
  2. Consultez le document original pour les outils, identifiants et environnements requis.
  3. Décrivez les entrées et le livrable souhaité ; comparez la sortie aux sources.
npx skills add https://github.com/lvlup-sw/exarchos --skill discover

Avant de commencer

  • L’installation n’inclut ni abonnement au modèle, ni quota API, ni accès aux fichiers.
  • Étoiles et installations reflètent l’activité, pas un test indépendant de qualité ou de sécurité.
Document Skill original

Rendu depuis le dépôt source en conservant titres, exemples, code, tableaux, liens et images.

Discovery Workflow Skill

A workflow type for tasks whose deliverable is a document, not code. It carries no verification gates (nothing to test), so the verification ladder does not apply.

When to Use

  • Competitive analyses and market research
  • Architecture comparisons and ADR scaffolding
  • Literature reviews and vendor evaluations
  • Design research that does NOT feed into implementation planning

When NOT to Use

  • If the deliverable includes code changes → use /exarchos:oneshot or /exarchos:ideate
  • If you need TDD enforcement → use any other workflow type
  • If the research feeds directly into implementation → use /exarchos:ideate (which authors the Design & Rationale section of the unified docs/specs/ artifact)

Discover bridge (the deep-rung escalation)

At the deep planning rung, /exarchos:ideate can escalate to this workflow as a first-class, event-linked research pre-pass instead of a manual "go start a new workflow" handoff. The bridge is opt-in (author-confirmed, never auto-run): the affordance is surfaced on next_actions, and the discover_bridge orchestrate action — invoked with confirm: true — stitches this discovery run to the originating spec by a deterministic correlationId (recorded as a state.patched link event on the feature stream). When you run a discovery escalated this way, cite the report path in the spec's ## Design & Rationale → Exploration section, and init this workflow with the bridge's correlationId so provenance spans both documents.

Phases

Phase 1: Gathering (initial)

Collect sources, references, and raw material for the deliverable.

  1. Define the research question or deliverable scope
  2. Identify and collect sources (URLs, documents, code references)
  3. Record sources in workflow state:
typescript
exarchos:exarchos_workflow({
  action: "update", featureId: "<id>",
  updates: { "artifacts.sources": ["<source1>", "<source2>", "..."] }
})
  1. Create an outline of the deliverable

Transition: When artifacts.sources is a non-empty array → synthesizing

Phase 2: Synthesizing

Draft the deliverable document from gathered sources.

  1. Write the document based on gathered sources and outline
  2. Commit the document to the repo (typically under docs/research/ or docs/designs/)
  3. Record the report path:
typescript
exarchos:exarchos_workflow({
  action: "update", featureId: "<id>",
  updates: { "artifacts.report": "<path-to-document>" }
})

Transition: When artifacts.report is set → completed

Optional: Escalation to Implementation

If discovery surfaces an implementation need:

  1. Note the finding in the report
  2. After completing the discovery workflow, start a new workflow:
bash
   ideate <implementation-topic>

Reference the discovery report as design input.

du même dépôt

Autres Skills

Tous les Skills
lvlup-sw
Communauté

checkpoint

Save and mutate workflow state — init a workflow, update fields, transition phases, and capture a structured handoff before context exhaustion. Use when the user says 'save progress', 'checkpoint', 'I need to stop', or runs /checkpoint. Writes current workflow phase, task progress, and artifacts to the event store for later resumption. Do NOT use for restoring/reading state after a session break (that is /rehydrate) or for workflow initialization framing handled by ideate/debug/refactor commands

Installations / 1h
1
GitHub Stars
19
Mis à jour
20 nov.
lvlup-sw
Communauté

git-worktrees

Git worktree management for parallel agent team development. Triggers: 'create worktree', 'worktree setup', or during /delegate dispatch. Do NOT use for branch creation without delegation context.

Installations / 1h
1
GitHub Stars
19
Mis à jour
20 nov.
lvlup-sw
Communauté

oneshot

Lightweight workflow for straightforward changes — plan → implement → optional PR. Direct-commit by default; synthesize is opt-in via synthesisPolicy or a runtime requestsynthesize event. Use for trivial fixes, config tweaks, single-file changes, or exploratory work that doesn't warrant subagent dispatch or two-stage review. Triggers: 'oneshot', 'quick fix', 'small change', or oneshot.

Installations / 1h
1
GitHub Stars
19
Mis à jour
20 nov.
lvlup-sw
Communauté

prune

Interactively prune stale non-terminal workflows from the pipeline. Use when the user says 'prune workflows', 'clean stale workflows', 'pipeline cleanup', or runs /prune. Runs a dry-run preview, displays candidates with staleness and safeguard skips, prompts the user to proceed/abort/force, then bulk-cancels approved workflows with a workflow.pruned audit event. Safeguards skip workflows with open PRs or recent commits unless force is set.

Installations / 1h
1
GitHub Stars
19
Mis à jour
20 nov.