Summary
The problem-solving workflow says the facilitator should never give time estimates, but later Step 7 explicitly asks for a timeline and writes to a timeline output slot.
Why this matters
The workflow currently contains conflicting guidance about whether time-oriented planning is allowed. That makes behavior ambiguous for both legacy and native-skill execution.
Current evidence
- Role/constraint text says: never give time estimates
- Step 7 asks:
What's the timeline?
- Step 7 emits a
timeline template output
- The method library also includes implementation guidance that asks about timeline
Suggested direction
Clarify whether the intended rule is:
- no speculative duration estimates, but sequencing/milestones are allowed, or
- no timeline output should be requested at all.
Related context
Observed while reviewing PR #7 (feat: convert problem solving to a native skill). This appears to be preserved legacy ambiguity, not native-skill conversion drift.
Summary
The problem-solving workflow says the facilitator should never give time estimates, but later Step 7 explicitly asks for a timeline and writes to a
timelineoutput slot.Why this matters
The workflow currently contains conflicting guidance about whether time-oriented planning is allowed. That makes behavior ambiguous for both legacy and native-skill execution.
Current evidence
What's the timeline?timelinetemplate outputSuggested direction
Clarify whether the intended rule is:
Related context
Observed while reviewing PR #7 (
feat: convert problem solving to a native skill). This appears to be preserved legacy ambiguity, not native-skill conversion drift.