You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[suite] [improvement] make spec ask the user instead of queuing pending decisions #71
I feel spec should be interactive and not completion-based, so that it does not emit pending decisions: if it is unsure of something, it directly asks me.
Today the skill is completion-oriented by design: a decision it cannot settle goes to a pending-decisions bundle and the run ends BLOCKED, with no separate interactive path. The wanted outcome is that a person present in the run gets asked in chat, the way discussion asks.
Two constraints already hold. Interaction posture is a fixed glossary term, so spec's classification moves with this. And cli/ is on hold, so what this does to the CLI's unattended spec stage is recorded as drift, not repaired. Related: #41, which asks the same of implementation.
Activity