agentleFS
Sign inStart free
wuwei-crgwuwei-crg/LXB-Framework/.agents/skills/trellis-start/SKILL.md

trellis-start

Skill301 starsChanged 6 months agoMITView on GitHub

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.

16 other projects use a version of this, 16 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use trellis-channel, trellis-session-insight and 1 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • wayfarer35Skill

    trellis-channel

    Use Trellis channel for live multi-agent collaboration, spawned workers, cross-agent review, progress inspection, forum channels, and channel log debugging.

    Also in 14 projects that use this

  • wayfarer35Skill

    trellis-session-insight

    Reach into past AI conversation history through the `trellis mem` CLI. Use whenever the user asks 'how did we solve X last time', 'have we discussed this before', 'what was the decision on X', 'remind me what we did in this task', '上次怎么解的', '之前讨论过吗', '想起一段对话', or when starting a brainstorm that overlaps prior work, debugging a familiar bug, continuing a task across sessions, or doing a finish-work review. Returns raw past dialogue; decide for the moment whether to update spec, append to task notes, quote inline in the answer, or just internalize.

    Also in 14 projects that use this

  • +1 more from wayfarer35

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 16 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    If this output includes a line beginning Trellis update available:, copy the full line verbatim when summarizing session context.

    line 19

“Common” is measured: kept by at least 6 in 10 of the 16 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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.

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

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

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

  • Active task + prd.md exists → Phase 2 step 2.1. Load the step detail:
    python ./.trellis/scripts/get_context.py --mode phase --step 2.1 --platform codex
  • 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 intentSkill
New feature / unclear requirementstrellis-brainstorm
About to write codetrellis-before-dev
Done coding / quality checktrellis-check
Stuck / fixed same bug multiple timestrellis-break-loop
Learned something worth capturingtrellis-update-spec

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

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free