Engineering manager
Your point of contact. Turns your goals into GitHub issues, coordinates the team, and manages delivery. Can merge under your explicit or standing authorization.
Many perspectives.
One shared project.
You work with the engineering manager.
The manager works with the team you define.
THE TEAM, IN MOTION Illustrative workflow
YOU Product owner
↕ requirements & decisions
↔ Cross-session collaborationGitHub issues → PRs
Engineering manager
Your point of contact. Turns your goals into GitHub issues, coordinates the team, and manages delivery. Can merge under your explicit or standing authorization.
Select a role to see its part in the process.
Tech lead
Shapes the technical approach, prepares the work, and reviews each pull request against its issue at an exact commit.
Software engineers
Work in parallel on assigned issues, each in a separate Claude Code session and git worktree. Run checks and open pull requests.
QA engineer
Exercises the behavior in a throwaway environment and reports pass, fail, or could not check, with evidence.
Security engineer
Examines sensitive changes, investigates privately reported concerns, and clears security holds before a merge.
Tech Writer
When needed, keeps READMEs, guides, and reference pages accurate and easy to find. Verifies commands and behavior against the code, and flags stale documentation to the EM.
UX Designer
When needed, shapes user flows and interface designs with the product owner, tech lead, and engineers. Configure this custom role with its own prompt in your team file.
A change has a path.
Define
You and the EM turn the goal into issues with acceptance criteria.
Prepare
The tech lead shapes the approach. The EM assigns a written brief to a seat.
Build
Engineers implement in their worktrees, run the gate, and open pull requests.
Review
The tech lead reviews the PR; QA verifies behavior; security examines sensitive changes.
Deliver
The Tech Writer keeps the guides and reference pages aligned with the change. The EM coordinates checks and merges. You merge, or delegate merging to the EM through an explicit or standing instruction.
Clear rules. Honest limits.
Prompts and skills define the team’s workflow; the launcher does not mechanically enforce every review step. Generated permission rules are accident guards, not a security boundary. All seats run as your OS user with your GitHub credential.
Read the full safety model →BUILT ON SHARED PRACTICESpecialize the roles.
Specialize the roles.
Make the handoffs explicit.
Fabrikito applies the practical patterns of a software factory: clear ownership, bounded assignments, independent review, and evidence before delivery.
For background on agent workflows, read Anthropic’s Building effective agents. Fabrikito is an independent open-source project.
YOUR NEXT PROJECT HAS A TEAM.Small factory.
Build your team ↗