lvlup-sw/exarchos

discover

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

ソースを見る

使い方

  1. インストールコマンドをコピーし、自分の環境へ導入する前にソースを確認します。
  2. 必要なツール、認証情報、対応環境を原文で確認します。
  3. 入力と成果物を指定し、出力を資料と照合します。
npx skills add https://github.com/lvlup-sw/exarchos --skill discover

開始前の確認

  • 導入にはモデル契約、API枠、ファイルへのアクセス許可は含まれません。
  • スター数や導入数は活動の指標であり、独立した品質・安全性試験ではありません。
リポジトリの原文

見出し、例、コード、表、リンク、参照画像を含む原文を表示しています。

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.

同じリポジトリから

関連する Skills

すべての Skills
lvlup-sw
コミュニティ

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

1時間の導入数
1
GitHub Stars
19
更新日
11月20日
lvlup-sw
コミュニティ

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.

1時間の導入数
1
GitHub Stars
19
更新日
11月20日
lvlup-sw
コミュニティ

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.

1時間の導入数
1
GitHub Stars
19
更新日
11月20日
lvlup-sw
コミュニティ

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.

1時間の導入数
1
GitHub Stars
19
更新日
11月20日