How it works

A guided pipeline from rough idea to proven branch.

Two stages, one funnel. Stage 1 shapes intent into a settled plan. Stage 2 turns the plan into session-sized tasks and executes them, with guardrails re-grounding intent at every gate. Nothing commits without you.

The feature pipeline

Stage 1 · Shape the planfrom raw thought to a settled, conflict-free roadmap

Capture

Rough ideas in, instantly

Typed, spoken ("Hey Spex"), or pulled from your IDE session. No forms, no filing.

grounding
gate

Research

Grounded in reality

Checked against your repo, existing plans, and past decisions before anything is promised.

conflict
check

Milestones & epics

A settled roadmap

Ideas slot into milestones and epics. Drift and conflicts are resolved while they are still cheap.

Pre-execution alignment gate: a human approves the plan

Stage 2 · Execute and provefrom approved plan to a branch that explains itself

Task breakdown

Session-sized cuts

Epics split into tasks sized to one context window, sequenced by dependency.

Dispatch

Agent gets full context

The next unblocked task ships to your agent as a context pack: spec, decisions, memories, guardrails.

Build

In your IDE, your tools

Claude Code, Cursor, any harness. Protocols keep the agent on-spec while it works.

Plan receipt

Proven, then shipped

Plan versus actual with evidence. You review drift and approve.

↺ lessons and decisions from every receipt feed back into memory, so the pipeline gets smarter each pass

plan receiptHS-STRP-TASK · branch spex/HS-STRP-stripe-setup

Wire Stripe setup into the onboarding state machinebuilt as plannedsrc/billing/onboarding-machine.ts · +38 -6

Persist setup-intent status across refreshbuilt as plannedsrc/billing/stripe-setup.ts · +61 -0

In-process retry queue for failed setup callsreused the gateway retry path with idempotency keyscommit 4f2a91c · lesson HS-WBHK-LES applied

planned 3 · built 3 · drift 1Approve receiptRequest changes

Workflows & protocols

The pipeline lives inside your IDE.

HeySpex ships as workflows and protocols for your agentic harness: Claude Code, Cursor, and friends. Slash commands run the pipeline without leaving the terminal, and protocols keep every agent session inside the guardrails.

✓Slash commands for every stage: capture, plan, next, brief✓Protocols enforce plan-first behavior inside the agent session✓Works with any harness. The vault is the shared source of truth.

More on hooks, skills, and MCP in Agent workflows →

$ /hs-next
→ next up:HS-STRP-TASK Connect Stripe setup
→ context pack: spec · 2 decisions · 1 lesson
→ protocol: plan-first · confirm scope before edits

$ /hs-capture "exports need rate limits"
→ filed asHS-CAP-R8LX· grounded, queued for research

$ /hs-brief
→ receipt drafted ·1 drift flagged· awaiting your approval

Memory · this project14 active

DECISIONGate middleware blocks new users only. Existing sessions stay live.2d

LESSONStripe webhooks need idempotency keys. Retries double-charged in staging.1w

DISCOVERYExport API already rate-limits at the gateway. App-level limit unnecessary.3w

New memory proposed from session 4f2aApproveEdit

Memory

Memories you control, not a black box.

Decisions, lessons, and discoveries are first-class records in your vault: visible, editable, and yours to keep or retire. Agents draw on them in every context pack, so nothing gets re-discovered or silently forgotten.

✓Discover once, reuse forever. Lessons persist across sessions.✓Review, edit, or retire any memory. AI proposes, you dispose.✓Plain markdown with frontmatter: greppable, diffable, portable.

Guardrails

Guided through the funnel, never off a cliff.

Every gate re-grounds intent before execution. Guardrails do not slow you down. They are what makes it safe to go fast.

grounding

Reality check at capture

Every idea is checked against the actual codebase before it becomes a plan.

drift check

Plans stay aligned

New work is compared against everything already decided, so contradictions surface early, while they are still cheap.

protocol

Agents stay on-spec

In-session protocols keep the agent inside scope: plan-first, confirm before edits, no silent expansions.

human gate

You hold the pen

AI proposes, you dispose. Plans, memories, and receipts all wait for your approval. Nothing commits without you.

See the pipeline run on your own repo.

HeySpex is in private beta. Request an invite, and when a seat opens, pick a branch and see the receipt.

Request an invite See pricing