singularity/singularity-forge
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions 1

docs(sf): disambiguate ADR-011 in PREFERENCES.md template too

Browse source 
Same fix as df095b406 but for the user-facing PREFERENCES.md template
that ships in /sf init projects. Reading "ADR-011 P2: mid-execution
escalation" without the gsd-2 prefix sends operators to SF's local
ADR-011 ("Swarm Chat and Debate Mode") which has nothing to do with
escalation.

Markdown-only.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This commit is contained in:
Mikael Hugo 2026-05-02 23:07:13 +02:00
parent df095b406a
commit f1fc8cc86b
1 changed files with 6 additions and 5 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

11
src/resources/extensions/sf/templates/PREFERENCES.md
View file

@ -32,12 +32,13 @@ phases:
skip_reassess:
reassess_after_slice:
skip_slice_research:
# ADR-011: progressive planning. When true, the milestone planner can mark
# slices as sketches (is_sketch=1, sketch_scope=<2-3 sentence hint>) and
# refine-slice expands each one just-in-time using prior slice summaries
# as context. When false (default), all slices get full plans up front.
# gsd-2 ADR-011 P1: progressive planning. When true, the milestone planner
# can mark slices as sketches (is_sketch=1, sketch_scope=<2-3 sentence
# hint>) and refine-slice expands each one just-in-time using prior slice
# summaries as context. When false (default), all slices get full plans up
# front. (Note: SF's local ADR-011 is "Swarm Chat" — unrelated.)
progressive_planning:
# ADR-011 P2: mid-execution escalation. When true, sf_task_complete honors
# gsd-2 ADR-011 P2: mid-execution escalation. When true, sf_task_complete honors
# an optional escalation: { question, options, recommendation, ... } payload.
# The agent's choice carries forward as a hard constraint into the next
# executor. See escalation_auto_accept for whether auto-mode pauses or