trellis-before-dev
Discovers and injects project-specific coding guidelines from .trellis/spec/ before implementation begins. Reads spec indexes, pre-development checklists, and shared thinking guides for the target package. Use when starting a new coding task, before writing any code, switching to a different package, or needing to refresh project conventions and standards.
git clone --depth 1 https://github.com/fy-agent/fyagent /tmp/trellis-before-dev && cp -r /tmp/trellis-before-dev/.cursor/skills/trellis-before-dev ~/.claude/skills/trellis-before-devSKILL.md
Read the relevant development guidelines before starting your task. Execute these steps: 1. **Read current task artifacts**: - `prd.md` for requirements and acceptance criteria - `design.md` if present for technical design - `implement.md` if present for execution order and validation plan 2. **Discover packages and their spec layers**: ```bash python ./.trellis/scripts/get_context.py --mode packages ``` 3. **Identify which specs apply** to your task based on: - Which package you're modifying (e.g., `cli/`, `docs-site/`) - What type of work (backend, frontend, unit-test, docs, etc.) - Any spec/research paths referenced by the task artifacts 4. **Read the spec index** for each relevant module: ```bash cat .trellis/spec/<package>/<layer>/index.md ``` Follow the **"Pre-Development Checklist"** section in the index. 5. **Read the specific guideline files** listed in the Pre-Development Checklist that are relevant to your task. The index is NOT the goal — it points you to the actual guideline files (e.g., `error-handling.md`, `conventions.md`, `mock-strategies.md`). Read those files to understand the coding standards and patterns. 6. **Always read shared guides**: ```bash cat .trellis/spec/guides/index.md ``` 7. **For a non-trivial task, state the change boundary before writing code.** Non-trivial means it touches more than one file, crosses a layer, changes a public interface, or edits code you did not just write. Write down: - the smallest behavior gap between what happens now and what should happen - where that behavior actually lives (not where it is easiest to intercept) - which files you expect to change, and why each one is necessary - what you are explicitly not doing in this task - if a local refactor is needed, how you will show it did not change behavior A small, well-scoped change does not need this — do it directly. If the real scope turns out to be clearly larger than this, say so and why before continuing. Do not widen the change on your own. 8. Understand the coding standards and patterns you need to follow, then proceed with your development plan. This step is **mandatory** before writing any code.
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.
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.
Use Trellis channel for live multi-agent collaboration, spawned workers, cross-agent review, progress inspection, forum channels, and channel log debugging.
Comprehensive quality verification: spec compliance, lint, type-check, tests, cross-layer data flow, code reuse, and consistency checks. Use when code is written and needs quality verification, before committing changes, or to catch context drift during long sessions.
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.
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.
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.
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.