skills.rest
saxonthune
saxonthuneCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

carta-spec-builder

Generate consistent specification files in a .carta/ workspace across abstraction levels.

1|Updated Jan 19, 2026
Search Tags:#documentation automation#requirements elicitation#structured documentation#architecture specs#spec builder#carta workspace#code shape specs
One-click install
npx skills add https://github.com/saxonthune/carta --skill carta-spec-builder
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: carta-spec-builder
Source: https://github.com/saxonthune/carta/tree/main/.claude/skills/carta-spec-builder
Command: npx skills add https://github.com/saxonthune/carta --skill carta-spec-builder

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

carta-spec-builder helps you turn messy product, domain, and implementation thinking into consistent specification files inside a Carta workspace, without writing code or inventing facts.

Core Features & Use Cases

  • Build spec files at any abstraction level: Create research, business domain, business process, architecture, or code-shape specs that match the user’s current understanding.
  • Maintain .carta structure and one-concern-per-file discipline: Ensures each output file targets a single concern and respects existing spec groups and layout.
  • Use a guided elicitation protocol with guardrails: Asks the right questions for the selected level and records unknowns as open questions instead of guessing.

Quick Start

Use the carta-spec-builder skill to generate the right .carta spec files for your project starting from your current level of detail (for example: research → entities → services → code shapes).

Frequently Asked Questions about carta-spec-builder

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I structure specification files for different abstraction levels?▼

You can build specification files at research, business domain, business process, architecture, or code-shape abstraction levels to match your current project understanding. This ensures structured documentation across multiple layers.

What is the best way to elicit architecture specs without inventing domain rules?▼

Elicit architecture specs using a guided protocol with guardrails that records unknowns as open questions instead of guessing. This prevents invented domain rules and ensures accurate service boundary documentation.

How do I maintain one concern per file discipline in a .carta workspace?▼

Maintain one concern per file discipline by enforcing guardrails that only write to .carta specs and detect existing spec group structure. This keeps your documentation layout organized and consistent.

Can I define code-shape module interfaces starting from high-level research?▼

Yes, you can generate spec files starting from your current level of detail and progress through research, entities, services, and code shapes. This supports workflows from initial topic research to defining module interfaces.

Does structured documentation automation work for mapping business processes and decisions?▼

Structured documentation automation works for mapping business processes and decisions by using a guided elicitation protocol. It asks the right questions for the selected level to accurately describe your business workflows.

Related Skills

Explore More Software Engineering Skills→
rkz91rkz91
264

gsd-new-project

Initialize new project workflows and generate planning artifacts.

Community
Advanced
openharmonyinsightopenharmonyinsight
31

oh-pdd-code-generator

Generate OpenHarmony service code frameworks from PDD design documents.

Official
Advanced
vZulinvZulin

speckit-git-commit

Stage and commit changes after Spec Kit commands complete.

Community
Intermediate
nobu007nobu007

agent-creator

Generate standardized Markdown agent definitions for the Miyabi framework.

Community
Advanced