Skip to main content

Ship your first feature

You make a request in the Software Factory, and ACE Dev 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.

Send the request. ACE Dev 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.

ACE Dev 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 Comments tab showing the agents' reasoning.

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.

You are never locked in

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

Step 5: Test in the local environment and approve the card​

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

Test before you approve

Do not approve on the summary alone. Open a local environment from the card, run the feature, and check that it works the way you want. Do this before you approve the card and before you merge any pull request.

If something is wrong or missing, do not fix it by hand and do not merge anyway. Choose Request changes on this last approval gate and describe what needs to change. The agents update the implementation, and the card comes back to the same gate. Test again in the local environment. Repeat as many times as you need.

Only approve the card once the feature works the way you want. Approving the commit and pull request sends the pull request to your GitHub repository.

Step 6: Review and merge the pull request in ACE Dev​

You do not need to leave ACE Dev to merge. Open Software Factory → Pull requests and select the pull request for your card. The review page shows the description, the changed files, the PR analysis, and the Summary panel with the source branch, commits, and status.

If automatic PR analysis is off, click Run analysis first. Approve and Merge stay blocked until an analysis has completed.

From the Summary panel you can:

  • Approve the pull request.
  • Merge it. Pick a merge strategy and confirm.
  • Reject it, with a reason.

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, and testing the result in a local environment before you approved it. The agents never touch your code without your sign-off.

Next steps​

  • Try Talk to ACE Dev 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.