autospec-listen

Route mid-conversation intents to autospec workflows for issue filing or spec writing.

3|1|Updated Apr 29, 2026

Search Tags:#automation #spec writing #github issues #agent workflows #intent routing #conversation listening

Ready to run

npx skills add https://github.com/berlinguyinca/autospec --skill autospec-listen

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: autospec-listen
Source: https://github.com/berlinguyinca/autospec/tree/main/skills/autospec-listen
Command: npx skills add https://github.com/berlinguyinca/autospec --skill autospec-listen

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It removes friction from mid-conversation planning by automatically recognizing when you want to file an issue or start a spec, then routing you into the right autospec workflow without forcing slash commands.

Core Features & Use Cases

Intent-based issue drafting: when you say an issue trigger phrase, it reads recent conversation context, drafts a structured issue body, asks you to confirm, and creates a GitHub issue labeled needs-classify.
Spec routing without duplication: when you use a spec trigger phrase, it confirms intent and hands off to /autospec-define for the full planning flow.
Deterministic router for build/review verbs: for imperative build/design/spec/review requests, it gates routing via listener-match.sh and then dispatches to the mapped autospec skill with an opt-out.

Quick Start

Say "file an issue" and then approve the drafted Goal/Context/Suggested AC to create a categorized GitHub issue.

Frequently Asked Questions about autospec-listen

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I automatically file GitHub issues from a chat conversation?▼

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.

Can I start writing spec documents without using slash commands?▼

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.

How does intent routing work for build and review requests?▼

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.

What is the best way to turn mid-conversation intents into structured spec actions?▼

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.

Do I need to manually categorize GitHub issues created from agent workflows?▼

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.

When should I not use automated conversation listening for issue filing?▼

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.