Agent skill

Architect Design Tree

by ntorga in ntorga/agent-starter-kit

Builds the design tree for the grill — decisions mapped as nodes with dependencies, recommendations, and impact, pruned by path.

MITAuto-check passedAI & LLM Engineering

Install Architect Design Tree

skills CLI
$ npx skills add ntorga/agent-starter-kit --skill architect-design-tree -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install ntorga/agent-starter-kit architect-design-tree --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/ntorga/agent-starter-kit.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/architect-design-tree .claude/skills/architect-design-tree && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
architect-design-tree
GitHub stars
146
Token cost
~1.2k tokens
SKILL.md length
666 words
Files
1
Skills in repo
21
Repo updated
First seen
Licence
MIT

At a glance

Builds the design tree for the grill — decisions mapped as nodes with dependencies, recommendations, and impact, pruned by path.

  • Works in 9 steps: Read the task block. Note the selected… → Orient in the codebase before mapping… → Identify the decisions the feature must… → …
  • AI & LLM Engineering work in your project
  • SKILL.md covers Purpose, Procedure, Tree Format and Handoff, plus 1 more section
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Architect Design Tree is an agent skill from ntorga/agent-starter-kit. Builds the design tree for the grill — decisions mapped as nodes with dependencies, recommendations, and impact, pruned by path.

Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in AI & LLM Engineering. The repository describes itself as: The scaffold for your multi-model, personalized Natural Language AI Harness (NLAH) . The licence is MIT.

When your agent uses it

  • AI & LLM Engineering work in your project

Example prompts

  • “Use the architect-design-tree skill to build the design tree for the grill — decisions mapped as nodes with dependencies, recommendations, and…”
  • “/architect-design-tree”

Workflow steps

9 steps, taken from the first numbered list in SKILL.md.

  1. Read the task block. Note the selected path (beginner, tinkerer, or pro) and any new user answers it carries.
  2. Orient in the codebase before mapping decisions
  3. Identify the decisions the feature must settle. Map them as a tree with three branches
  4. Apply the quality filter to every candidate decision: does this decision pivot the destination substantially? If the answer does not…
  5. Check the ceilings. Business: 30 (beginner, tinkerer), 100 (pro). Architecture: 10 (tinkerer), 100 (pro). Implementation: 100 (pro). If a…
  6. For each node, write
  7. List the facts the tree needs from the codebase or the environment in the ## Facts section. A fact is a question only a lookup can answer…
  8. Write the tree to .memory/plan//tree.md in the format below. Create the directory if it does not exist.
  9. For re-tree: read tree.md. Add the new nodes with their fields. Add new facts if needed. Keep every settled node and every settled fact as…

What it can do on your machine

Read from SKILL.md and the folder at commit 851e942. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Architect Design Tree loads about 1.2k tokens when it runs. Until then it costs about 38 tokens; SKILL.md has 666 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~38
When it runs · the whole SKILL.md, loaded when a task matches
~1.2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from ntorga/agent-starter-kit at commit 851e942, republished under its MIT licence (© ntorga). 666 words, ~1,199 tokens.

Download SKILL.mdSave it as .claude/skills/architect-design-tree/SKILL.md (or your agent's skills folder).
name
architect-design-tree
description
Builds the design tree for the grill — decisions mapped as nodes with dependencies, recommendations, and impact, pruned by path.
usedBy
architect
version
0.2.2
lastUpdated
2026-09-12

Purpose

The grill interviews the user over the design tree. This skill builds and extends that tree. The tree is the grill's working state: every decision the feature must settle, mapped with its dependencies, pruned to the selected path, ranked by impact. The Maestro computes the frontier from this file and works the rounds. You never talk to the user.

Procedure

  • Initial — no tree exists. Build the tree from the task prompt.
  • Re-tree — the tree exists. The user's answers opened a branch the tree does not have. Extend the tree. Do not rebuild it.
  1. Read the task block. Note the selected path (beginner, tinkerer, or pro) and any new user answers it carries.
  2. Orient in the codebase before mapping decisions:
    • Read .context.md files in the affected directories.
    • Read docs/FEATURE-MAP.md if it exists.
    • For the beginner path, infer the default architecture from the maintenance, lightweight, and safe principles (KISS, single responsibility, safe boundaries — rules/code/general.md).
  3. Identify the decisions the feature must settle. Map them as a tree with three branches:
    • Business — what the user wants. Acceptance criteria, scope, constraints, success conditions.
    • Architecture — how the system is structured. Directory layout, layer separation, frameworks, reference projects.
    • Implementation — how the work is organized. Epics, dependencies, parallelizable groups. Prune branches the path does not explore. Beginner: business only. Tinkerer: business and architecture. Pro: all three.
  4. Apply the quality filter to every candidate decision: does this decision pivot the destination substantially? If the answer does not change the project's direction, remove the node. Prune with the filter, not the ceiling. The ceiling only bounds how large a branch grows — never pad the tree to hit it.
  5. Check the ceilings. Business: 30 (beginner, tinkerer), 100 (pro). Architecture: 10 (tinkerer), 100 (pro). Implementation: 100 (pro). If a branch exceeds its ceiling, prune until it fits.
  6. For each node, write:
    • The question in plain terms the user can answer alone.
    • Dependencies — the node numbers that must settle first. A node may also depend on a fact from step 7.
    • Recommendation — the answer you would choose, with the reason, in one or two sentences.
    • Impact — high, medium, or low, by how many downstream nodes the answer unblocks.
  7. List the facts the tree needs from the codebase or the environment in the ## Facts section. A fact is a question only a lookup can answer — a library capability, an existing endpoint, a config key. Number them f1, f2, and so on.
  8. Write the tree to .memory/plan/<feature-slug>/tree.md in the format below. Create the directory if it does not exist.
  9. For re-tree: read tree.md. Add the new nodes with their fields. Add new facts if needed. Keep every settled node and every settled fact as is. Never renumber.
Show full SKILL.md (150 more words)Show less

Tree Format

# Design Tree: <Feature Name>
Path: <beginner | tinkerer | pro>

## Business
1. [settled] <question> — answer: <settled answer>
2. [open] <question> — depends: 1 — recommendation: <answer and why> — impact: high

## Architecture
1. [open] <question> — depends: B2 — recommendation: <answer and why> — impact: medium

## Implementation
1. [open] <question> — depends: B1, A1, f1 — recommendation: <answer and why> — impact: low

## Facts
- f1: <fact question> — open
- f2: <fact question> — <found answer, with source>
  • Number nodes per branch, starting at 1. Refer to a node in another branch by prefix: B2, A1, I1.
  • A node with no dependencies is frontier from round 1.
  • A node is frontier when every dependency is settled: a node marked [settled], or a fact with a found answer.

Handoff

Deliver tree.md with a summary:

## Summary
[One sentence: what was done]

## Tree
- Branches explored: [list]
- Branches pruned: [list and why]
- Facts needed: [list]

Guardrails

  • Never ask the user a question. You deliver the tree. The Maestro relays it.
  • Never leave a decision silently assumed. If the feature must settle it, it gets a node.
  • Never rebuild on re-tree. Extend. Settled nodes keep their numbers and answers.
  • Never put a codebase fact inside a user question. It goes in ## Facts as a fact dependency.
  • Keep questions answerable by the user alone. If answering requires a file read, it is a fact, not a question.
  • Write the tree in STE-100. Short sentences. One idea per sentence. Active voice.

© ntorga, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/architect-design-tree of ntorga/agent-starter-kit.

Open the folder on GitHubat commit 851e942

Compare with similar skills

Architect Design Tree next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Architect Design Tree compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Architect Design Tree this skillntorga/agent-starter-kit146—~1.2kAutomated safety check: PassMIT
Agent BuildershareAI-lab/learn-claude-code78k6 repos~1.2kAutomated safety check: PassMIT
Add Uint Supportpytorch/pytorch104k2 repos~2.3kAutomated safety check: PassCustom licence
Peft Fine TuningOrchestra-Research/AI-Research-SKILLs13k9 repos~3.1kAutomated safety check: PassMIT
Segment Anything Model GuideOrchestra-Research/AI-Research-SKILLs13k9 repos~3.3kAutomated safety check: PassMIT
1passwordtrpc-group/trpc-agent-go1.8k15 repos~656Automated safety check: PassApache-2.0

Similar skills

  • Agent Builder

    shareAI-lab/learn-claude-code

    Design and build AI agents for any domain. An agent skill from shareAI-lab/learn-claude-code.

    78k GitHub starsUsed in 6 repos~1.2k tokens
    AI & LLM EngineeringAuto-check passed
  • Add Uint Support

    pytorch/pytorch

    Add unsigned integer (uint) type support to PyTorch operators by updating ATDISPATCH macros.

    104k GitHub starsUsed in 2 repos~2.3k tokens
    AI & LLM EngineeringAuto-check passed
  • Peft Fine Tuning

    Orchestra-Research/AI-Research-SKILLs

    Parameter-efficient fine-tuning for LLMs using LoRA, QLoRA, and 25+ methods.

    13k GitHub starsUsed in 9 repos~3.1k tokens
    AI & LLM EngineeringAuto-check passed
  • Segment Anything Model Guide

    Orchestra-Research/AI-Research-SKILLs

    Guide to using Meta's Segment Anything Model for zero-shot image segmentation with point, box or mask prompts, or automatic mask generation.

    13k GitHub starsUsed in 9 repos~3.3k tokens
    AI & LLM EngineeringAuto-check passed
  • 1password

    trpc-group/trpc-agent-go

    Set up and use 1Password CLI (op). An agent skill from trpc-group/trpc-agent-go.

    1.8k GitHub starsUsed in 15 repos~656 tokens
    AI & LLM EngineeringAuto-check passed
  • Chroma Vector Database

    Orchestra-Research/AI-Research-SKILLs

    Shows how to store documents and embeddings in Chroma, query them by similarity with metadata filters, and persist them to disk for RAG and semantic search projects.

    13k GitHub starsUsed in 8 repos~2.3k tokens
    AI & LLM EngineeringAuto-check passed

More from ntorga/agent-starter-kit

All 21 skills in this repo
  • Agent Decision

    ntorga/agent-starter-kit

    Deterministic self-evaluation rubric for decision escalations — scored every run using the FRAME framework.

    146 GitHub stars~1.7k tokensUpdated 26 days ago
    Auto-check passed
  • Agent Memory

    ntorga/agent-starter-kit

    Long-term and session memory across sessions. An agent skill from ntorga/agent-starter-kit.

    146 GitHub stars~2.7k tokensUpdated 26 days ago
    Auto-check passed
  • Architect Impl Grounding

    ntorga/agent-starter-kit

    Grounds the grill's settled decisions in the codebase — annotates impl.md with file paths, signatures, reference files, test specs, and LOC; re-grounds the next epic after each landing.

    146 GitHub stars~944 tokensUpdated 26 days ago
    Auto-check passed
  • Boot

    ntorga/agent-starter-kit

    Session startup — gitignore, auto-update, memory, rules, context, CLI config, and greet.

    146 GitHub stars~937 tokensUpdated 26 days ago
    Auto-check passed
  • Browser Inspect

    ntorga/agent-starter-kit

    Browser inspection and interaction for verifying rendered web UI during development.

    146 GitHub stars~2k tokensUpdated 26 days ago
    Auto-check passed
  • Code Coherence Review

    ntorga/agent-starter-kit

    Reviews code and plans for logic coherence, correctness, and structural integrity.

    146 GitHub stars~2.8k tokensUpdated 26 days ago
    Auto-check passed

Questions about Architect Design Tree

What does Architect Design Tree do?

Builds the design tree for the grill — decisions mapped as nodes with dependencies, recommendations, and impact, pruned by path. Architect Design Tree is an agent skill from ntorga/agent-starter-kit. Builds the design tree for the grill — decisions mapped as nodes with dependencies, recommendations, and impact, pruned by path.

When should I use Architect Design Tree?

Architect Design Tree fits situations like: AI & LLM Engineering work in your project.

How do I install Architect Design Tree in Claude Code?

Run `npx skills add ntorga/agent-starter-kit --skill architect-design-tree -a claude-code`. Or copy the skill folder (skills/architect-design-tree in ntorga/agent-starter-kit) into .claude/skills/architect-design-tree in your project. Claude Code loads it when a task matches its description.

How do I install Architect Design Tree in Codex?

Run `npx skills add ntorga/agent-starter-kit --skill architect-design-tree -a codex`. Or copy the skill folder (skills/architect-design-tree in ntorga/agent-starter-kit) into .agents/skills/architect-design-tree in your project. Codex loads it when a task matches its description.

Can I use Architect Design Tree in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add ntorga/agent-starter-kit --skill architect-design-tree -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/architect-design-tree, .gemini/skills/architect-design-tree, .github/skills/architect-design-tree and .opencode/skills/architect-design-tree in your project.

What does Architect Design Tree need to run?

SKILL.md names no scripts, command-line tools or credentials: Architect Design Tree is instructions for the agent only.

Does Architect Design Tree access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Architect Design Tree safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Architect Design Tree use?

Architect Design Tree is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Architect Design Tree use?

About 1.2k tokens (SKILL.md is roughly 4.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Architect Design Tree?

Skills that share tags, products or a category with Architect Design Tree: Agent Builder (shareAI-lab/learn-claude-code, 78k stars), Add Uint Support (pytorch/pytorch, 104k stars), Peft Fine Tuning (Orchestra-Research/AI-Research-SKILLs, 13k stars) and Segment Anything Model Guide (Orchestra-Research/AI-Research-SKILLs, 13k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Architect Design Tree?

ntorga (a GitHub user) maintains it in ntorga/agent-starter-kit, which has 146 GitHub stars. The repository holds 21 skills in this directory. The repository was last updated on September 12, 2026.

Source: ntorga/agent-starter-kit on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.