IDEAFY DOCS

Recipe — Ship a feature from Ideation to Completed

The canonical end-to-end flow. A single feature goes through every column in order, with the agent driving the transitions you'd expect to drive by hand.

1. Capture

You have an idea. Click the + button on the Ideation column. Type a title and a short description. Save.

Tip. Spend 90 seconds writing a half-decent description. The rest of the recipe works much better with 90 seconds of context than with 10.

You now have a card in Ideation.

2. Evaluate

Open the card. In the modal header, click Evaluate. The card locks; processingType = evaluate starts.

Behind the scenes, the agent reads the card, loads the Product Narrative, and considers the idea against your project's non-goals, target users, and success metrics. When it's done it calls save_opinion with the full template — Summary Verdict, Strengths, Concerns, Recommendations, Priority, Final Score — and sets a positive or negative verdict.

You read the Opinion tab. If the verdict is negative and the concerns are solid, drag the card to Withdrawn and stop. If the verdict is positive (or you disagree with the negative), move on.

3. Triage

Drag the card to Backlog. It now sits in your queue of scoped work.

4. Plan

When you're ready to start, open the card and switch to the Solution tab. In the chat panel, tell the agent what you want to build. Have a conversation — the agent may ask clarifying questions, read source files, propose alternatives. Iterate until you both agree on the shape of the change.

When the agent is confident, it calls save_plan. Two things happen:

  1. A complete plan appears in the Solution tab — prose, changed-files table, step-by-step walkthrough, risks
  2. The card moves to In Progress automatically (because save_plan always does that)

5. Build

You now have a few options:

  • Autonomous. Click Run autonomous in the card modal header. The agent creates a worktree, starts a dev server on an allocated port, writes the code, commits, and — when done — calls save_tests to move the card to Human Test
  • Interactive. Click Open in Terminal. A terminal spawns in the worktree with the agent ready; you pair-program until the work is done. You (or the agent) call save_tests when ready
  • Manual. You just want to write the code yourself. Start work via the modal (creates the worktree and branch), then use your normal editor. When done, call save_tests from the chat panel

Whichever path you pick, the card is in In Progress with an active worktree, an active branch, and (usually) an active dev server on its own port. You can see the branch name and port on the card surface.

6. Test

When implementation is done, the card is in Human Test with a populated Tests tab — a checkbox list of acceptance criteria. Walk through the list:

  • Launch the dev server URL (port is shown on the card)
  • Exercise each criterion by clicking or typing
  • Tick the corresponding box

If something is wrong, you don't need to hop back to the Solution tab or open an IDE. Stay on the Tests tab and drive the fix from its chat panel. With --dangerously-skip-permissions enabled on the session, the agent can:

  • Read and write source files in the worktree
  • Run the test suite and read the output
  • Drive the browser to reproduce the failure
  • Edit, commit, and push the fix
  • Call save_tests again to update the checkbox list

This is the step in the recipe where non-technical teammates shine. A product owner or business analyst describing "the email validation is wrong, fix it and commit" is enough — the chat panel translates that into code, tests, and a commit. Your existing ticks are preserved if the agent regenerates the tests.

7. Ship

All tests pass. In the card modal header, click Merge. Ideafy rebases the branch onto main:

  • If the rebase is clean, the worktree is removed, the branch is merged, and the card moves to Completed
  • If there are conflicts, Ideafy surfaces a Resolve Conflict panel with the file list. Click Auto-resolve with Claude (spawns a Claude session in the worktree) or Open in Terminal to fix them by hand, then retry the merge

Once merged, the card lands in Completed. The dev server stops. The worktree is cleaned up. completedAt is set.

8. Review

Open Completed with the This Week filter. The card is at the top. You can scroll back to Detail, Opinion, Solution, Tests to see what you shipped — and to the conversations if you want to audit how you got there. Completed cards are read-only but fully explorable.

Prev: Team settings Next: Close a bug with quick-fix Up: User guide index

Last updated: 2026-04-13