64 lines
2.5 KiB
Markdown
64 lines
2.5 KiB
Markdown
---
|
|
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.
|
|
|
|
```bash
|
|
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.
|
|
|
|
```bash
|
|
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.
|
|
|
|
```bash
|
|
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:
|
|
```bash
|
|
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 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`.
|