Exécutez n'importe quel Skill dans Manus
en un clic

Exécutez n'importe quel Skill dans Manus en un clic

trellis-start

Étoiles11 894

Forks671

Mis à jour15 juin 2026 à 06:25

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.

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Exécuter dans Manus

Source

mindfold-ai

mindfold-ai/Trellis

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Exécuter dans Manus

Métiers associésSOC

Basé sur la classification professionnelle SOC

Développeurs de logicielsProfessions informatiques et mathématiques·SOC 15-1252

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 compact context by following these steps.

Step 1: Current state

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

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

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 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:

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

Plus depuis ce dépôt

même dépôt

trellis-meta

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, workflows, the channel runtime (trellis channel), bundled runtime agents under .trellis/agents/, selectable workflow templates, registry-backed spec refresh, cross-session memory (trellis mem) generated by trellis init, or AI-facing bundled skills (trellis-channel, trellis-session-insight, trellis-spec-bootstrap) and bundled-skill auto-dispatch flow.

2026-07-0611.9k

create-manifest

mindfold-ai/Trellis

Create a Trellis migration manifest and matching docs-site changelogs for a target release by analyzing commits since the previous release. Use when preparing a patch, beta, rc, or minor release manifest.

2026-06-2511.9k

trellis-brainstorm

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.

Guide requirements discovery for a Trellis task after task-creation consent. Use when the user is ready to clarify requirements before implementation.

2026-06-2411.9k

trellis-break-loop

mindfold-ai/Trellis

Deep bug analysis to break the fix-forget-repeat cycle. Analyzes root cause category, why fixes failed, prevention mechanisms, and captures knowledge into specs. Use after fixing a bug to prevent the same class of bugs.

2026-06-1811.9k

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 compact context by following these steps.

Step 1: Current state

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

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

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 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:

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