Repository navigation
Problem-solving workflow asks for a timeline while also forbidding time estimates #11
Description
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
timelinetemplate 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.
Activity
bmadcode commentedon Aug 29, 2026
Thanks @dickymoore — you were right that this is contradictory: the problem-solving workflow tells the facilitator never to give time estimates, then Step 7 asks for a timeline and writes to a
timelineoutput slot.Closing as part of a backlog sweep. CIS is being restructured for distribution through
npx skills(PR #43), and the workflow content is going to be revisited as part of that work rather than patched in place now.If the contradiction is still there once the restructure lands, please reopen or file a fresh one — it's a legitimate report and it won't be waved away a second time.
🤖 Posted by BMad Bot on behalf of the maintainers.
If this resurfaces on a current version, please reopen or file a fresh issue — it will be looked at. Questions and ideas are always welcome in Discord.