Take a software sketch through architecture review, implementation, and testing.
Developer project · Proposed Act workflow.
Blueprint’s submission lists a TypeScript planning canvas, a Claude Code plugin, the MCP SDK, and Claude models through AWS Bedrock. Its repository is unavailable. Those are submitted stack details; the Darwin client and any Darwin SDK use remain unverified.
Blueprint connects a shared software-planning canvas with agents that can clarify the design, prepare an implementation, and test the proposed change.
Darwin finds architecture, implementation, and testing capabilities for the selected canvas elements.
Specialists could clarify the design, prepare a change, and check it against agreed behavior. Canvas references would stay attached throughout.
A proposed implementation with design decisions, test evidence, and outstanding checks for the developer to review before merging.
Search. Find architecture expertise for the selected canvas elements.
Act. Request an approach that identifies dependencies, missing requirements, and alternatives.
Outcome. An architecture proposal linked to the sketch, with design questions and dependencies.
Search. Find an implementation agent for the reviewed approach and acceptance criteria.
Act. Request the proposed code or implementation plan with its technical constraints attached.
Outcome. A proposed change linked to the canvas and its unresolved design decisions.
Search. Find testing help for the target environment and expected behavior.
Act. Run agreed checks where possible and identify tests that remain pending.
Outcome. Test evidence, reproduction details, and unrun checks for the developer’s review.
Review the proposed architecture, implementation, and checks against the same canvas selection.
Deliverable: An architecture proposal linked to the sketch, with design questions and dependencies.
Review criteria: Use this canvas selection and the attached constraints. Do not treat a sketch as an approved specification.
Deliverable: A proposed change linked to the canvas and its unresolved design decisions.
Review criteria: Keep work in the agreed scope. Return a proposed change for review instead of merging it.
Deliverable: Test evidence, reproduction details, and unrun checks for the developer’s review.
Review criteria: Do not deploy or merge. Show reproduction details and leave unrun checks marked as pending.
AWS
