Run any Skill in Manus with one click

$pwd:

trellis-start

Name: Trellis Start
Author: mindfold-ai

// 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.

Run Skill in Manus

$ git log --oneline --stat

stars:8,671

forks:471

updated:May 7, 2026 at 11:58

SKILL.md

readonly

name	trellis-start
description	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 Session

Initialize a Trellis-managed development session. This platform has no session-start hook, so manually load the equivalent context by following these steps (each one mirrors a section the hook would otherwise inject).

Step 1: Current state

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

python3 ./.trellis/scripts/get_context.py

Step 2: Workflow overview

Phase Index + skill routing table + DO-NOT-skip rules.

python3 ./.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.

python3 ./.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. Check the task directory:

Active task + prd.md exists → Phase 2 step 2.1. Load the step detail:
```
python3 ./.trellis/scripts/get_context.py --mode phase --step 2.1
```
Active task + no prd.md → Phase 1.1. Load the trellis-brainstorm skill.
No active task → when the user describes multi-step work, load the trellis-brainstorm skill to clarify requirements, then create a task via task.py create. For simple one-off questions or trivial edits, skip this and just answer directly — no task needed.

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.

related-skills.json

same repository

brainstorm.md

from "mindfold-ai/Trellis"

Collaborative requirements discovery session optimized for AI coding workflows. Creates task directories, seeds PRDs, runs codebase research, proposes concrete implementation approaches with trade-offs, and converges on MVP scope through structured Q&A. Use when requirements are unclear, multiple implementation paths exist, trade-offs need evaluation, or a complex feature needs scoping before development.

2026-05-088.7k

trellis-finish-work.md

from "mindfold-ai/Trellis"

Wrap up the current session: verify quality gate passed, remind user to commit, archive completed tasks, and record session progress to the developer journal. Use when done coding and ready to end the session.

2026-05-068.7k

trellis-meta.md

from "mindfold-ai/Trellis"

Understand and customize the local Trellis architecture inside a user project. Use when modifying .trellis plus platform hooks, settings, agents, skills, commands, prompts, or workflows generated by trellis init.

2026-05-068.7k

finish-work.md

from "mindfold-ai/Trellis"

Wrap up an active Trellis task: archive it (and any other completed-but-unarchived tasks the user wants to clean up) and record a session journal. Refuses to run if the working tree has uncommitted code changes (those belong in workflow Phase 3.4 first). Use when the user asks to finish / wrap up / call it a day, or invokes $finish-work.

2026-05-068.7k

trellis-continue.md

from "mindfold-ai/Trellis"

Resume work on the current task. Loads the workflow Phase Index, figures out which phase/step to pick up at, then pulls the step-level detail via get_context.py --mode phase. Use when coming back to an in-progress task and you need to know what to do next.

2026-04-308.7k

trellis-brainstorm.md

from "mindfold-ai/Trellis"

Guides collaborative requirements discovery before implementation. Creates task directory, seeds PRD, asks high-value questions one at a time, researches technical choices, and converges on MVP scope. Use when requirements are unclear, there are multiple valid approaches, or the user describes a new feature or complex task.

2026-04-288.7k

package.json

"author": "mindfold-ai"

"repository": "mindfold-ai/Trellis"

View GitHub Repository View Creator Repositories

$ install --global

$ download --local

Run Skill in Manus

$ useful --forSOC

Software DevelopersComputer and Mathematical Occupations15-1252L4

name	trellis-start
description	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 Session

Step 1: Current state

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

python3 ./.trellis/scripts/get_context.py

Step 2: Workflow overview

Phase Index + skill routing table + DO-NOT-skip rules.

python3 ./.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.

python3 ./.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. Check the task directory:

Active task + prd.md exists → Phase 2 step 2.1. Load the step detail:
```
python3 ./.trellis/scripts/get_context.py --mode phase --step 2.1
```
Active task + no prd.md → Phase 1.1. Load the trellis-brainstorm skill.
No active task → when the user describes multi-step work, load the trellis-brainstorm skill to clarify requirements, then create a task via task.py create. For simple one-off questions or trivial edits, skip this and just answer directly — no task needed.

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.

trellis-start

Start Session

Step 1: Current state

Step 2: Workflow overview

Step 3: Guideline indexes

Step 4: Decide next action

Skill routing (quick reference)

More from this repository

More from this repository

Start Session

Step 1: Current state

Step 2: Workflow overview

Step 3: Guideline indexes

Step 4: Decide next action

Skill routing (quick reference)