Ideas
Ideas is where you work out what to build with a coding agent before adding tickets to the board. A conversation belongs to one project, so the agent can read the repository and ground its suggestions in the code you already have.
Ideas also uses project knowledgebases enabled for the Plan phase. Each reply receives their maps and rules and can read relevant pages, helping proposals follow existing conventions and decisions. The purple knowledge indicator shows the supplied sources and reported read activity. See using project knowledge in Ideas for the controls.
A draft proposal in Herdloom’s demo UI. Expand each ticket to explore the work before accepting it.
Describe, refine, accept
Section titled “Describe, refine, accept”Describe the outcome. Pick an agent, model, and effort, then explain who the change helps and what a good result looks like. Specs, notes, and screenshots can supply the context.
Refine the proposal. The agent can ask questions or propose a set of tickets. Proposed work includes descriptions, acceptance criteria, sizes, dependencies, and simple concept sketches. Reply to change the scope; earlier proposals stay in the conversation for reference.
Accept the work. Accepting the latest proposal adds that batch of tickets to the project’s backlog. Their dependencies and acceptance criteria go with them, along with every context file sent in the conversation so far. The tickets use the project’s execution defaults.
Where Ideas meets the board
Section titled “Where Ideas meets the board”An idea conversation and its draft proposals are separate from the board. Discussing a proposal does not queue a ticket or start its implementation. Once accepted, the tickets follow the same board workflow as tickets you write yourself or import from a tracker.
Accepting an idea proposal is also separate from approving a ticket’s implementation plan. If a ticket uses planning, the agent works out how to implement it when the ticket runs, and that plan follows the project’s approval settings.
For a new app, the scaffold should be a prerequisite for features that need its files. You can queue the whole proposal: dependent tickets wait for the scaffold to merge, then independent features can run together. Herdloom checks the prerequisite code is available before starting each ticket.
One conversation can grow
Section titled “One conversation can grow”Keep prompting after accepting a proposal to add more work to the same idea. Earlier accepted proposals keep their ticket links; accepting a later proposal adds only the new batch.
The accepted tickets are in the backlog. The follow-up is still a draft in the composer, ready to continue the same conversation.
New proposals can depend on tickets accepted earlier in the same conversation, so adding more work does not bypass an unfinished foundation.
Files you send later are included in future batches. Tickets already created keep their existing attachments. Deleting the conversation removes its drafts but keeps accepted tickets and the uploaded files those tickets still reference.
Start with an idea takes you through your first proposal. How to use Ideas covers attachments, revisions, and continuing a conversation. Tickets explains what each accepted card holds, and Your first ticket follows the work from Backlog to a reviewed change.