- name
SKILL.md
The skill file stays in the publisher's repository.
Paste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add fy-agent/fyagent --skill trellis-before-dev -a cursor -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add fy-agent/fyagent --skill trellis-before-dev -a claude-code -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add fy-agent/fyagent --skill trellis-before-dev -a codex -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add fy-agent/fyagent --skill trellis-before-dev -a grok -ySend the copied message in a Grok Bot chat. The Bot fetches this SKILL.md from GitHub and adds it to the skills all your Bots share.
Install this skill: https://github.com/fy-agent/fyagent/tree/HEAD/.agents/skills/trellis-before-devFrom the publisher
Read the relevant development guidelines before starting your task.
Execute these steps:
Read current task artifacts:
prd.md for requirements and acceptance criteriadesign.md if present for technical designimplement.md if present for execution order and validation planDiscover packages and their spec layers:
python ./.trellis/scripts/get_context.py --mode packages
Identify which specs apply to your task based on:
cli/, docs-site/)Read the spec index for each relevant module:
cat .trellis/spec/<package>/<layer>/index.md
Follow the "Pre-Development Checklist" section in the index.
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.
Always read shared guides:
cat .trellis/spec/guides/index.md
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:
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.
Understand the coding standards and patterns you need to follow, then proceed with your development plan.
This step is mandatory before writing any code.
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 pac
---name: trellis-before-devdescription: Discovers and injects project-specific coding guidelines from .trellis/spec/ before implementation begins…---# .agents/skills/trellis-before-dev/SKILL.mdOverview
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.
FAQ
Download .agents/skills/trellis-before-dev/SKILL.md from the publisher, or copy the path and open the repository. PlugMCP lists the skill and does not host the file.
The publisher keeps it at https://github.com/fy-agent/fyagent.
Claude, Cursor, Codex, and Grok Build can read a SKILL.md you add from the publisher's repository. Grok Bot installs it when you send the skill's GitHub folder link in a chat.