Generates formatted planning tasks from analysis of a Carta workspace and MCP document summaries.
npx skills add https://github.com/saxonthune/carta --skill carta-builder
Please help me install this Agent Skill. Skill: carta-builder Source: https://github.com/saxonthune/carta/tree/main/.claude/skills/carta-builder Command: npx skills add https://github.com/saxonthune/carta --skill carta-builder
Carta-builder converts ambiguous design directions into structured, user-validated planning artifacts by investigating a Carta .carta/ workspace and the associated MCP Carta document, then producing only todo-tasks/ for an implementer.
.carta/ structure plus Carta’s document/model summaries to understand constructs and schemas without reading source code.todo-tasks/ (including optional epic files) that include motivation, design decisions, and a required verifiability section.Ask the AI to evaluate the current Carta workspace and propose a concrete design plan, then create the needed todo-tasks/ based on your chosen direction.
High-intent search queries and answers about installing and using this skill.
You can convert design explorations into deterministic planning artifacts by investigating the Carta `.carta/` workspace and MCP document summaries, then generating structured `todo-tasks/` files with motivations and verifiability sections.
To plan features without source-code access, use Carta document and model summaries to understand schemas and constructs, enabling tradeoff-focused design discussions that clarify scope and constraints before implementation.
Generate todo-tasks for architecture investigations by compiling MCP document summaries and workspace structures to guide decisions, enforcing no code edits and writing only to `todo-tasks/` using specified epic and task formats.
No, carta-builder does not require source-code access. It explicitly enforces no source-code reads and no code edits, relying entirely on workspace and document compilation outputs to guide design decisions and produce planning artifacts.
Yes, you can use Carta document summaries to evaluate design tradeoffs. The process helps you choose between options, clarifies scope and constraints, and documents the decision rationale before any implementation begins.
Todo-tasks must follow a specified epic and task format that includes motivation, design decisions, and a required `## Verifiability` section to ensure deterministic, implementer-ready planning artifacts.
cartaCreate investor records in Carta CRM via the MCP server.
ysyecustAutomate end-to-end project verification across builds, type checks, linting, tests, and security scans.
izzoaExplore ideas, requirements, and codebase context to clarify problems before implementation.
ConradmakerTranslate vague UI ideas into structured design prompts and briefs.