Sculptured docs

Examples and templates

Every starting point that ships with Sculptured — what each agent does, how work flows, and when to pick it.

Pick the smallest example that fits your work, then change it. Every agent, Job, folder and arrow stays editable on the Design board before you start.

Built-in templates

Press New project to see them. Agents run on chooses Claude or Codex for every agent before the project is made.

TemplateAgentsShapePick it when
Solo agent1 ClaudeOne agentYou want one agent with the board's controls and evidence. Start here.
Builder → ReviewerBuilder (Claude), Reviewer (Codex)Builder hands work to ReviewerOne change, checked by a second vendor.
Planner → 2 BuildersPlanner, Builder 1, Builder 2Planner hands one piece to each builderThe work splits into two independent pieces.
Blank canvasnone—You know the shape you want.
Textbook creator9 Codex agents in two groupsA workflow: Input → dispatched topics → review loops → assemblyTurning sources into interactive textbook sections. See the textbook example.
Adaptive support teamSupport coordinatorOne agent that creates specialists only when neededLearning dynamic dispatch with spawn_agent (CS2680).
Independent reviewersClarity reviewer, Evidence reviewer, EditorTwo reviewers hand work to the EditorTwo independent opinions, then a synthesis (CS2680 committee).
Design and reviseDesigner, ReviewerDesigner hands work to Reviewer, who may send bounded feedback back by messageA short design with one round of review (CS2680 pipeline with a retry edge).

The last three are small teaching exercises with fictional inputs written into their Jobs: a support ticket, a mini-essay and a habit-tracker spec. They make no real changes, so they show how a pattern behaves before you use it on real work.

Official examples in Community

Two complete teams are published in Community by Sculptured examples. Open Community, find the block, and press Add to project. The block arrives in your Library for review, then goes into a project like any saved group.

gstack-style product team

Eight Claude agents take one feature through a small product team's sprint. The roles and order are inspired by gstack by Garry Tan (MIT). Every Job is written in Sculptured's own words, and the example is not made or endorsed by the gstack author. gstack doesn't need to be installed.

flowchart LR
  PR["Product reviewer"] --> DE["Designer"] --> EL["Eng lead"] --> BU["Builder"]
  BU --> CR["Code reviewer"]
  BU --> QA["QA"]
  CR --> RM["Release manager"]
  QA --> RM
  RM --> RE["Retro"]
GroupAgentDoes
Think & planProduct reviewer (CEO lens)Challenges the request and writes PLAN.md: goal, scope, success criteria, open questions.
Think & planDesignerAdds screens, flows and empty, error and loading states to PLAN.md.
Think & planEng lead (architect)Adds the components to change, data flow, risks, tests and ordered steps.
BuildBuilderImplements the steps with tests on a feature branch, in small commits.
Review & QACode reviewerReviews the branch's diff, fixes small issues, lists findings and gives a verdict.
Review & QAQARuns the tests and uses the feature like a user; reports bugs with steps to reproduce.
ShipRelease managerRuns the tests again, updates release notes and docs, writes the pull-request description.
ReflectRetroWrites RETRO.md: what shipped, what slowed the team down, what to change next time.

Every arrow is "hands work to", with no workflow, so work moves forward once. Code reviewer and QA run in parallel, and the Release manager waits for both.

Use it for a feature in an existing repository, when you want planning, review and QA as separate steps you can read. Before you start: set the project folder to your repository, and put what you want built in the Product reviewer's Job. These are real Claude agents and may cost money.

Coding hospital

A workflow that treats a repository's issues like patients. It is modelled on Cockroach Labs' "running a hospital for code" experiment.

AgentRole
Triage NurseThe dispatcher. Reads ISSUES.md in the project folder and dispatches one item per issue.
FellowWorks each item up (reproduce, find the cause, plan) and then treats it (fixes it).
Senior FellowTakes over an item's Treatment from round 3, after two failed rounds.
Review AttendingApproves the plan only if it fixes the cause and names the test that proves it.
Correctness Reviewer, Safety ReviewerThe code-review panel. Both must approve.
Charge NurseChanges nothing. Every 30 minutes a scheduled board round asks it to summarise what is waiting, blocked or escalated.
Discharge NurseThe assembly. Writes the final report once every item has finished.

How an item moves:

  1. Admit? A person admits the issue, or closes it as not-a-bug or wont-fix.
  2. Workup → Plan review. The Fellow plans; the Review Attending approves or sends it back.
  3. Treatment → Tests. The Fellow fixes it; Sculptured runs npm test. A failure goes back to Treatment.
  4. Code review. A two-reviewer panel; any changes vote sends it back.
  5. Sign-off → Merge. A person ships it; Sculptured merges the item's branch into main. A conflict goes back to Treatment.
  6. Escalation. After 4 Treatment rounds, a person decides: retry or wont-fix.

It also turns on per-item copies and branches, a guard (npm test every 15 minutes) and a decision log. The full diagram is on the workflows page.

Use it for a backlog of small, well-described issues in a repository with tests. Before you start: the project folder must be a git repository with an ISSUES.md and an npm test script, or change the check and guard commands to your own. People decide at Admit?, Sign-off and Escalation, so plan to answer decision cards.

Choose an example

I want one change made and checked

Builder → Reviewer. Add a Check such as npm test on the Builder so the result is verified, not only reported.

I have a feature, not a task list

The gstack-style product team. Remove roles you don't need; fewer agents cost less.

I have many small issues

The Coding hospital. Start with two or three issues and a low Maximum items while you learn how it behaves.

I want to learn the patterns first

The three CS2680 templates, then the pattern catalog.

Next steps