skysynth

SkyDiscover-Synthesize (SkySynth): The Lead Workflow

You are the lead. The user names a system to build. You run the three stages of the SkySynth architecture below, handing each box to its role agent, and deliver a specialized system: proven or tested, benchmarked, assumptions explicit.

 Initial Specification        Synthesis Loop                          Final Deliverables
 ┌──────────────────────┐     ┌────────────────────────────────┐      ┌──────────────────────┐
 │ Spec Builder         │     │ Planner ─► Coding Agent        │      │ Specialized system   │
 │  ─► Specification    │ ──► │    ▲          │ (code, or      │ ──►  │  + tests or proof    │
 │  requirements,       │     │ Critic ◄─ Evaluator ─► Auditor │      │  + score and spec.md │
 │  environment,        │     │           correctness,  hack → │      │                      │
 │  workload, formal    │     │           performance   test   │      │                      │
 │  spec (optional)     │     │                 code + proof)  │      │                      │
 └──────────────────────┘     └────────────────────────────────┘      └──────────────────────┘
        Phase 1                          Phase 2                             Phase 3

The lead sequences the work, resolves handoffs, records decisions, and reports the result. It never does a role's job itself; each role writes its own files.

Files

The agents/ tree is the pipeline: one brief per role, filed under the phase that runs it.

workflow/
├── SKILL.md                  this file: the lead's procedure
├── agents/                   role briefs (agents/README.md is the map)
│   ├── 1-specification/      spec-builder, kb-builder (optional, background)
│   └── 2-synthesis-loop/     planner, coding-agent, dsa, isa, evaluator, auditor, critic
│                             (Phase 3 is the auditor's final review modes)
├── references/               shared rules; read one when its concern comes up
│   ├── artifacts.md          the run directory, who owns each file, the published result
│   ├── verification.md       tests, measurement rules, audits, release claims
│   └── state.md              the decision log, asking the user, state kept across runs
├── scripts/                  the test tools: validate_test, run_tests, the release checks;
│                             kb/ is the wiki schema and kbtool.py (find, page, validate, index)
├── hooks/                    the delivery hook and the clone-reuse guard the agent harness runs
└── adapters/                 entry points for Claude Code, Codex, and pi (Cursor needs none)