autospec-listen

You can automatically file GitHub issues from chat by using intent-based issue drafting, which reads recent conversation context, drafts a structured Goal/Context/Suggested AC body, asks for confirmation, and creates an issue labeled needs-classify.

Yes, you can start writing specs without slash commands by saying a spec trigger phrase during a conversation; the system confirms your intent and hands off directly to the autospec-define workflow for full planning.

Intent routing for build and review requests works by using deterministic trigger matching to identify imperative verbs, gating the request via listener-match.sh, and dispatching to the mapped autospec skill with an opt-out option.

The best way to turn mid-conversation intents into spec actions is through deterministic routing that recognizes imperative goals like filing issues or starting design specs, drafts confirmation-ready content, and delegates to downstream autospec skills.

No, manual categorization is not required immediately; GitHub issues created from agent workflows are automatically labeled needs-classify, allowing your team to review and categorize them after the automated drafting and confirmation process.

You should not use automated conversation listening when your chat scenario lacks clear imperative goals or when you prefer manual control over issue creation, as the system relies on deterministic trigger matching to initiate the drafting and routing workflow.