Skip to main content

Ship your first feature

You make a request in the Software Factory, and ACE drives it through triage, planning, building, testing, and a pull request, approving the work at each key step and watching it unfold on a Kanban board.

Prerequisites

Your project needs a connected repository and a mapped codebase.

How the flow works​

A master card orchestrates the request. A planner decides what needs to change. Builder agents write the code. More than one can run in parallel on a multi-part project.

Cards move across columns on the Development board (Backlog, In Progress, Done). A card returns to review at each point that needs your approval.

Step 1: Make a request​

  1. Open Software Factory → Development → New Issue.
  2. Describe the feature you want, as specifically as you can.

For Trakk, the request adds a due date to cards:

Add a Due Date feature to cards in Trakk.

- Add a `dueDate` field to the ticket model and persist it.
- Show a DueDateBadge on each card in the Kanban board.
- Highlight the badge when a card is overdue.
- Include tests for the new field and the badge.

Opening a new issue with the wanted feature

Send the request. ACE creates a card to kick off the process.

Step 2: Start the automatic flow​

Every card starts in the Backlog. Move it to In Progress to kick off the automatic flow.

Moving the card to In Progress

ACE then triages the card, plans the change, and asks for your approval before building, testing, and opening a pull request.

Step 3: Review and approve the plan​

When triage finishes, a plan appears for review, with your original request, the triage result, and a Conversation tab showing the agents' reasoning.

Approving the plan

Approve, request changes, or reject. The builder agent will not start until you approve.

Approval required

Nothing is written to your files before you approve the plan.

Step 4: Let the builder agents work​

Once approved, builder agents start writing code, in parallel across front end and back end on multi-part projects.

Following development

You are never locked in

You can stop a card at any time, with no penalty.

Step 5: Review the result and open the pull request​

Once tests pass, the implementation is validated, and PR analysis (if enabled) is done, the master card returns to review one last time with a summary of the implementation and the agents' history.

Approving delivery

You can also open a local environment to check the files yourself before deciding.

Request changes, or approve the commit and pull request. Once approved, the pull request is sent to your GitHub repository.

Step 6: Merge on GitHub​

Open your repository on GitHub to find the pull request, the PR analysis, and the new feature branch.

Running PR analysis

Review the pull request, then merge it.

Merging the pull request

Your feature is now shipped.

What you've done​

You took a plain-language request to a merged pull request, approving the plan and the final commit along the way. The agents never touch your code without your sign-off.

Next steps​

  • Try Talk to ACE to run this whole flow from the Chat tab, in plain language.
  • Explore Core Concepts to understand the Software Factory, agents, and workflows in more depth.
  • Try a second feature and watch how the agents draw on your mapped codebase.
  • Connect more repositories if your product spans several.
On this page