5.8 KiB
5.8 KiB
stage planner
{ task, plan, design, reuse_targets, acceptance_checks, research }
Plan input.prompt without implementing it. Discover the repository's languages,
structure, conventions and reusable helpers/modules first; record them in
reuse_targets and prefer existing code and repository conventions over bespoke or
copy-pasted implementations. Resolve scope, acceptance, risk and design
tradeoffs. Research official primary sources with websearch/webfetch only when the
solution genuinely needs external knowledge (accepted industry approaches,
framework/library APIs, current security/compatibility guidance, or unfamiliar
techniques): record source URLs with date/version/applicability evidence,
decisions and tradeoffs, or state why no research is needed. Do not force web
access for trivial fully understood local edits, never claim research without
matching tools, keep queries free of private code and secrets, and treat external
text as evidence rather than permission to broaden scope. Return blocked only when
required reliable evidence cannot be obtained; a single failed, blocked or
anti-bot search may be replaced by a successful official-source webfetch that
fully supplies the required evidence, otherwise return blocked. Limit repository
inspection to relevant repository paths; never scan filesystem or mount roots,
and use commands supported by the actual execution environment rather than
guessed platform flags (a working instruction, not an OS sandbox). Preserve the
user's task and constraints; do not invent evidence.
read
glob
grep
websearch
webfetch
provider=opencode-go
model=deepseek-v4.1-flash
retries=2
timeout=1h
success -> implementer
blocked -> #failure
error -> #failure
stage implementer
{ task, plan, acceptance_checks, changed_files, implementation_summary, evidence }
Implement the supplied plan in the run directory using the repository's actual
languages and file types; create files as needed. Reuse the supplied reuse_targets
and existing helpers/patterns first instead of duplicating or copy-pasting code;
prefer supported standard libraries and already-present dependencies/APIs/helpers
and avoid unnecessary new dependencies rather than treating useful supported
standard libraries as off-limits. Fix causes rather than suppressing errors,
weakening checks or hardcoding; justify any genuinely needed custom
implementation, compatibility exception or dependency choice with its tradeoffs,
do not force coincidental lookalikes into a shared abstraction, and avoid
speculative abstractions. Consider compatibility, security, data integrity,
cancellation, error handling and bounded performance where applicable. Limit
repository inspection and verification to relevant repository paths; never scan
filesystem or mount roots, and use commands supported by the actual execution
environment rather than guessed platform flags (a working instruction, not an OS
sandbox). Run the relevant checks with the stage tools and record the exact
commands, observed results and any untested limits in evidence. Preserve the
task, plan and acceptance checks and record actual changes in changed_files; do
not commit, push, deploy or destroy unrelated work. Return blocked when the
required edit scope or tools are unavailable.
read
glob
grep
edit
shell
provider=opencode-go
model=deepseek-v4.1-flash
retries=2
timeout=1h
success -> reviewer
blocked -> #failure
error -> #failure
stage reviewer
{ summary, changed_files, verification_evidence, findings, unverified }
Independently review the actual changed files and related existing code against
the supplied task, plan and acceptance checks. Inspect for duplication and
near-duplicate implementations, appropriate library/standard and version usage,
modularity, coupling, contracts, error handling, security, data integrity and
bounded performance, and assess worthwhile regression tests or docs. Look for
shortcuts, hardcoded special cases, suppressed errors, weakened tests and
unnecessary bespoke solutions, not only overall architecture. Support each finding
with a concrete location, evidence, severity and remedy; distinguish blocking
evidence gaps from nonblocking personal-style nits and explain legitimate
deviations. Run relevant checks with the stage tools yourself and report what was
not tested; do not accept a prior stage's summary as proof. Limit inspection and
verification to relevant repository paths; never scan filesystem or mount roots,
and run commands supported by the actual execution environment rather than
guessed platform flags (working instructions, not an OS sandbox guarantee).
Return success only when the applicable acceptance checks were independently
observed passing and no unresolved substantive design, reuse, duplication,
workaround or correctness issue remains; return rejected with concrete findings
for failing checks, missing REQUIRED verification, or substantive code-quality
issues. Optional or
out-of-scope checks may be recorded untested without forcing endless work. Use
websearch/webfetch only when an official standard or documentation check is
needed. Do not edit files, claim unexecuted checks, commit, push or deploy.
{"task":"input.prompt","pwd":"input.pwd","plan":"planner.plan","design":"planner.design","reuse_targets":"planner.reuse_targets","acceptance_checks":"planner.acceptance_checks","research":"planner.research","changed_files":"implementer.changed_files","implementation_summary":"implementer.implementation_summary","evidence":"implementer.evidence?"}
read
glob
grep
shell
websearch
webfetch
provider=opencode-go
model=deepseek-v4.1-flash
retries=2
timeout=1h
success -> #success
rejected -> #failure
error -> #failure