Plan & Ship
Agent Teams are where Codelit builds and runs the work. Plan & Ship carries a team and its evidence into the product and engineering artifacts needed to deliver it.
Start with the proven workflow
A successful run reveals the roles, tools, approvals, outputs, and failure paths the supporting system must handle. Plan & Ship uses that accepted workflow as context instead of inventing a separate delivery plan from scratch.
- Keep the Agent Team and its History in the same project.
- Review the latest successful receipt before generating an artifact.
- Resolve missing tools or unclear approvals before treating the workflow as delivery evidence.
Choose one delivery output
Generate only the artifact the next owner needs. Product Plans capture requirements and milestones. Architecture captures system boundaries and dependencies. Repo packs combine the runnable Agent Team with accepted planning artifacts, delivery tasks, traceability, verification, and a redacted run receipt. GitHub creates a new repository from that same bundle.
- Open the Project that owns the Agent Team.
- Open Plan & Ship and confirm the selected Project, Agent Team, accepted Product Plan, accepted Architecture, and run receipt.
- Resolve any visible missing-source warnings, or continue knowing the manifest will preserve them.
- Download the repo pack or create the GitHub handoff. If a source changed after preview, reopen Plan & Ship before exporting.
Review before accepting
Codelit previews structural additions, removals, and edits when a generated Product Plan or Architecture differs from accepted work. Acceptance is explicit, so regeneration never silently replaces the artifact your team already approved.