Short answer: focus a GitHub issue body, pull request description, project draft item, project item note, or comment field. Press ⌃+⌥+R (Mac) or Ctrl+Alt+R (Windows/Linux), dictate acceptance criteria, test plan, and status update prose. Press again to insert. Add labels, iteration, assignee, and status in GitHub. AICHE does not move cards, edit custom fields, or call the GitHub API.
Why This Matters In GitHub Projects
A project item tied to an issue needs more than a title. Status fields, iteration, milestone, and custom priority columns only help when the linked issue or PR body explains scope, risk, and test intent. Voice fills those text surfaces without leaving the board view.
GitHub-Native Workflows
Issue template completion with actual acceptance criteria
Many repos use issue templates with sections like:
- steps to reproduce
- expected behavior
- acceptance criteria
- out of scope
Dictate all sections in one pass:
"Bug appears only on Safari 17 when checkout includes coupon and gift card. Expected behavior is combined discount application with final total update before payment submit. Acceptance criteria includes E2E test for Safari and Chrome. Out of scope: redesign of coupon UI."
This creates implementation-ready issues, not placeholders.
PR body quality while diff is visible
GitHub PR templates often require summary, changes, risk, and test plan. Dictate each block with specifics:
"Summary: replace client-side tax fallback with server-calculated totals. Risk: potential mismatch in legacy carts created before migration. Test plan: unit tests in cartTotals.spec.ts, manual checkout flow on staging tenant northwind, refund path regression."
Reviewers can approve faster when rationale is explicit.
Project draft items before conversion
In Projects, draft cards usually start as one line and stall. Before converting to an issue, dictate:
"Customer success request from ACME onboarding. Need export of seat-usage by department. Owner likely backend analytics. Target iteration next sprint. Dependency on event schema v2."
Now the converted issue lands with context from day one.
Project item notes and status transitions
When moving status from In Progress to In Review, dictate the transition note:
"API contract finalized, frontend pending snapshot updates. Blocking item is localization review for error messages. QA can begin on feature flag checkout_tax_v2."
Status changes become meaningful and auditable.
AI Inputs In GitHub Projects
If your team uses GitHub Copilot chat alongside Projects, AICHE helps in prompt fields for:
- issue drafting from project context
- PR summary/refactor prompts
- follow-up prompts that request tests or risk analysis
AICHE inserts prompt text. GitHub AI tools run generation.
How It Works
- Open issue, PR, project draft, or project item note in GitHub web.
- Focus the target text field.
- Press ⌃+⌥+R / Ctrl+Alt+R.
- Speak complete context: problem, scope, dependencies, and test intent.
- Press again to insert.
- Add labels, assignee, iteration, and status in GitHub.
Audio is streamed for cloud transcription, processed, and discarded immediately after processing, within 1 second. No persistent audio copy.
FAQ
Does AICHE set project fields or move status?
No. Text insertion only.
Does this work in GitHub web fields in a desktop browser?
Yes. This workflow targets GitHub web text fields opened in a desktop browser.
Should I still use templates?
Yes. Templates provide structure, dictation fills them with useful specifics quickly.
Try it now: pick one draft card in Projects, dictate full context and dependency notes, then convert it into a complete issue.