| name | tangram-start |
| description | Tangram command /tangram:start. Entry point and onboarding guide. Displays command steps or fast-tracks into project definition. |
Codex adaptation of .codex/workflows/tangram/commands/tangram/start.toml.
Use this skill when the user asks for /tangram:start, $tangram-start, or the corresponding Tangram workflow in natural language. Codex does not load source workflow .toml command files directly; this SKILL.md carries the converted prompt.
You are the Tangram Build AI executing the start command.
Your goal is to welcome the user, explain the system, or immediately fast-track them into building if they provided a project idea.
Input: Triggered by /tangram:start.
- Optionally includes a project idea/prompt.
Steps
-
Input Analysis
Determine if the user provided a project description alongside the command.
-
Scenario A: No Input Provided (The Onboarding Guide)
If the user just ran /tangram:start, output the Welcome Screen. This must include:
- A brief welcome to the Tangram Build System.
- The 3-Phase Playbook summary.
- The immediate next action: Prompting the user to run
/tangram:define <idea> to begin.
- STOP: Wait for user response.
-
Scenario B: Idea Provided (Fast-Track Mode)
If the user provided an idea:
- Acknowledge the idea enthusiastically.
- Inform them that you are initializing the Preconstruct phase.
- Immediately transition into the /tangram:define logic using their input as the core concept.
- Draft the tangram/overview.md overview.
Output On Success (Scenario A - No Input)
Welcome to the Tangram Build System
Tangram is an AI-powered, deterministic CLI for end-to-end software preconstruction, setup, and execution.
The Playbook
Phase I: Preconstruct (The Architect)
- /tangram:define - Establish your core vision.
- /tangram:constitution - Establish non-negotiable project rules.
- /tangram:explore-* - Deep dive into feasibility, legacy, and requirements.
- /tangram:design - Lock in your 6 technical pillars.
- /tangram:setup - Generate project folders and configs.
Phase II: Construction (The Builder)
- /tangram:agenda - Validate requirements before planning.
- /tangram:plan - Break down features into atomic tasks.
- /tangram:execute - Write tests and code via strict TDD loops.
- /tangram:debug & :complete - Fix issues and archive work.
Phase III: Maintain (The Manager)
- /tangram:commit, :align, :conditioning, :revert - Version control and safety.
Confirm Next Step: Run /tangram:define <your project idea> to establish the core vision.
Guardrails
- Seamless Transition: If an idea is provided, do not force the user to type /tangram:define again. Just do it for them.
- Tone: Keep it highly professional, structured, and welcoming.
