How do I install the Trellis Start skill?

Run npx skillmds@latest add fy-agent/trellis-start in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Trellis Start safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Trellis Start?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Trellis Start free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Trellis Start?

fy-agent (@fy-agent) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Trellis Start by fy-agent — Agent Skill

Name: Trellis Start
Author: fy-agent

Trellis Start

Initializes an AI development session by reading workflow guides, developer identity, git status, active tasks, and project guidelines from .trellis/. Classifies incoming tasks and routes to brainstorm, direct edit, or task workflow. Use when beginning a new coding session, resuming work, starting a new task, or re-establishing project context.

fy-agent e557bff 2.8 KB Updated Sep 17, 2026

File contents

Start Session

Initialize a Trellis-managed development session. This platform has no session-start hook, so manually load the equivalent compact context by following these steps.

Step 1: Current state

Identity, git status, current task, active tasks, journal location.

python ./.trellis/scripts/get_context.py

If this output includes a line beginning Trellis update available:, copy the full line verbatim when summarizing session context. Do not shorten operational command hints.

Step 2: Workflow overview

Compact Phase Index, request triage rules, planning artifact contract, and the step-detail command.

python ./.trellis/scripts/get_context.py --mode phase

Full guide in .trellis/workflow.md (read on demand).

Step 3: Guideline indexes

Discover packages + spec layers, then read each relevant index file.

python ./.trellis/scripts/get_context.py --mode packages
cat .trellis/spec/guides/index.md
cat .trellis/spec/<package>/<layer>/index.md   # for each relevant layer

Index files list the specific guideline docs to read when you actually start coding.

Step 4: Decide next action

From Step 1 you know the current task and status. Check the task directory:

Active task status planning + no prd.md → Phase 1.1. Load the trellis-brainstorm skill.
Active task status planning + prd.md exists → stay in Phase 1. Lightweight tasks can be PRD-only; complex tasks need design.md + implement.md. Load the relevant Phase 1 step detail before task.py start.

Active task status in_progress → Phase 2 step 2.1. Load the step detail:

python ./.trellis/scripts/get_context.py --mode phase --step 2.1 --platform codex

No active task → classify first. For simple conversation / small task, ask only whether this turn should create a Trellis task. For complex work, ask whether you may create a Trellis task and enter planning. If the user says no, skip Trellis for this session.

Skill routing (quick reference)

User intent	Skill
New feature / unclear requirements	`trellis-brainstorm`
About to write code	`trellis-before-dev`
Done coding / quality check	`trellis-check`
Stuck / fixed same bug multiple times	`trellis-break-loop`
Learned something worth capturing	`trellis-update-spec`

Full rules + anti-rationalization table in .trellis/workflow.md.

---name: trellis-startdescription: Initializes an AI development session by reading workflow guides, developer identity, git status, active tasks, and project guidelines from .trellis/. Classifies incoming tasks and routes to brainstorm, direct edit, or task workflow. Use when beginning a new coding session, resuming work, starting a new task, or re-establishing project context.---# Start SessionInitialize a Trellis-managed development session. This platform has no session-start hook, so manually load the equivalent compact context by following these steps.---## Step 1: Current stateIdentity, git status, current task, active tasks, journal location.```bashpython ./.trellis/scripts/get_context.py```If this output includes a line beginning `Trellis update available:`, copy the full line verbatim when summarizing session context. Do not shorten operational command hints.## Step 2: Workflow overviewCompact Phase Index, request triage rules, planning artifact contract, and the step-detail command.```bashpython ./.trellis/scripts/get_context.py --mode phase```Full guide in `.trellis/workflow.md` (read on demand).## Step 3: Guideline indexesDiscover packages + spec layers, then read each relevant index file.```bashpython ./.trellis/scripts/get_context.py --mode packagescat .trellis/spec/guides/index.mdcat .trellis/spec/<package>/<layer>/index.md # for each relevant layer```Index files list the specific guideline docs to read when you actually start coding.## Step 4: Decide next actionFrom Step 1 you know the current task and status. Check the task directory:- **Active task status `planning` + no `prd.md`** → Phase 1.1. Load the `trellis-brainstorm` skill.- **Active task status `planning` + `prd.md` exists** → stay in Phase 1. Lightweight tasks can be PRD-only; complex tasks need `design.md` + `implement.md`. Load the relevant Phase 1 step detail before `task.py start`.- **Active task status `in_progress`** → Phase 2 step 2.1. Load the step detail: ```bash python ./.trellis/scripts/get_context.py --mode phase --step 2.1 --platform codex ```- **No active task** → classify first. For simple conversation / small task, ask only whether this turn should create a Trellis task. For complex work, ask whether you may create a Trellis task and enter planning. If the user says no, skip Trellis for this session.---## Skill routing (quick reference)| User intent | Skill ||---|---|| New feature / unclear requirements | `trellis-brainstorm` || About to write code | `trellis-before-dev` || Done coding / quality check | `trellis-check` || Stuck / fixed same bug multiple times | `trellis-break-loop` || Learned something worth capturing | `trellis-update-spec` |Full rules + anti-rationalization table in `.trellis/workflow.md`.

Frequently asked questions