Dayflow

Vague idea in.
Build-ready issue out.

Dayflow is a planning workspace for GitHub Projects. It reads your repository, asks the questions a senior engineer would ask, and turns your answers into issues a developer can pick up without a meeting.

See how a session runs

Works with GitHub Projects v2 · your own token, encrypted per account

Planning Session · partsearch-site
live

New session · the idea as you said it

People keep asking to export their search results. Let them download what they searched for, probably CSV?

Reading partsearch-site before asking anything…

One session, four moves

A Planning Session is a short, structured conversation. It ends with work on your board, not a transcript.

  1. 1

    Describe the work

    Type the idea the way you would say it out loud. Paste screenshots straight into the session.

  2. 2

    Answer real questions

    The agent reads the codebase first, so every question is specific enough to be worth answering.

  3. 3

    Review draft tasks

    Each draft carries requirements, acceptance criteria, and tests. Approve the ones that are ready.

  4. 4

    Publish to GitHub

    Approved drafts become issues on your Project board. Status lives there from then on.

Questions that have read the code

Before asking anything, Dayflow checks your repository in a private local cache. Questions cite what is actually there: existing limits, current behavior, the edge case you forgot about.

Technical observations stay in your private Planning Notes. The published issue says what to build, not which files to edit.

Planning question

Saved searches already debounce input by 300ms in the suggestions hook. Should the new filter panel reuse that behavior or apply filters instantly?

lib/search/suggestions.tscomponents/filter-panel.tsx
Recommended: reuse the debounce so filtering feels consistent with search.

No idea is too early

Start a brainstorm when you only have a hunch. Pick a lens, think out loud with an agent that knows the repo, and promote the thread to a Planning Session once it firms up.

Start a brainstorm
ExploreNew feature ideasSecurity reviewPerformanceUX polishTechnical risk
“The repo already tracks per-user saved searches. A digest email of new matches might be a small step with real pull. Want to explore what it would touch?”

Opinionated where it counts

GitHub owns status

The board mirrors your Project fields exactly. Dayflow never invents a second source of truth.

Private by default

Tokens are encrypted per account, and planning notes never leak into published issues.

What, not how

Published tasks describe outcomes and acceptance criteria. Implementation stays with the developer.

Plan the next thing properly

Connect a repository and a Project board. Your first session takes about five minutes.

Dayflow