Skip to content

[suite] [improvement] make spec ask the user instead of queuing pending decisions #71

Open

Description

@Jei-sKappa

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

  1. added
    focus: nextThe single issue deliberately selected to be worked on next
    effort: 3Design plus implementation, tests and docs following
    on Sep 16, 2026
  2. removed
    focus: nextThe single issue deliberately selected to be worked on next
    on Sep 29, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    effort: 3Design plus implementation, tests and docs followingscope: suiteThe skill suite (suite/)type: improvementMakes an existing capability work better

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions