Parent
docs/issues/unic-archon-dlc/PRD.md
What to build
First half of the explore workflow: four parallel research agents converging on a synthesize node that produces a coherent brief, written to docs/workflow/<slug>/findings.md.
In scope:
.archon/workflows/explore.yaml (will be extended in slice 05 with the prototype phase)./unic-dlc-explore command file.- Four parallel research nodes running simultaneously, each scoped to a single concern:
research-stack — current and emerging stack relevant to the featureresearch-features — comparable existing features in the codebase and prior artresearch-architecture — how the change fits the existing architecture and ADRsresearch-pitfalls — known traps, deprecations, security/privacy considerations
synthesize node combining the four research outputs with the user's stated intent into a coherent brief. Pulls in CONTEXT.md and (if multi-context) CONTEXT-MAP.md so the brief uses the project glossary.docs/workflow/<slug>/findings.md is committed to the repo. The slug is taken from the user-supplied feature name; the hook creates the directory if absent.- Optional input from
explore is honoured by plan: plan works without findings, but consumes them when present (the contract is "findings.md may or may not exist" — slice 06's specs node handles both cases).
Out of scope (covered in slice 05): prototype node, VALIDATED/INVALIDATED/PARTIAL verdicts, spike-branch gate, spike ticket creation.
Acceptance criteria
Blocked by
PRD: docs/issues/unic-archon-dlc/PRD.md
Migrated from: docs/issues/unic-archon-dlc/04-explore-parallel-research-and-synthesize.md (source removed after migration)
Touched by PRs: #33
Parent
docs/issues/unic-archon-dlc/PRD.mdWhat to build
First half of the
exploreworkflow: four parallel research agents converging on asynthesizenode that produces a coherent brief, written todocs/workflow/<slug>/findings.md.In scope:
.archon/workflows/explore.yaml(will be extended in slice 05 with the prototype phase)./unic-dlc-explorecommand file.research-stack— current and emerging stack relevant to the featureresearch-features— comparable existing features in the codebase and prior artresearch-architecture— how the change fits the existing architecture and ADRsresearch-pitfalls— known traps, deprecations, security/privacy considerationssynthesizenode combining the four research outputs with the user's stated intent into a coherent brief. Pulls in CONTEXT.md and (if multi-context) CONTEXT-MAP.md so the brief uses the project glossary.docs/workflow/<slug>/findings.mdis committed to the repo. The slug is taken from the user-supplied feature name; the hook creates the directory if absent.exploreis honoured byplan:planworks without findings, but consumes them when present (the contract is "findings.md may or may not exist" — slice 06'sspecsnode handles both cases).Out of scope (covered in slice 05): prototype node, VALIDATED/INVALIDATED/PARTIAL verdicts, spike-branch gate, spike ticket creation.
Acceptance criteria
/unic-dlc-explore <slug>runs all four research nodes in parallel (verifiable from the Archon execution log or YAML structure).synthesizeproducesdocs/workflow/<slug>/findings.mdcontaining sections for each research dimension plus the integrated brief.findings.mdreferences CONTEXT.md vocabulary and at least one existing ADR by ID when one is relevant.explorewithout an existingdocs/workflow/<slug>/directory creates it; running with an existing directory does not destroy prior contents.unic-dlc-prefix.Blocked by
PRD:
docs/issues/unic-archon-dlc/PRD.mdMigrated from:
docs/issues/unic-archon-dlc/04-explore-parallel-research-and-synthesize.md(source removed after migration)Touched by PRs: #33