trellis-before-dev

Loads .trellis/spec development guidelines and checklists before coding tasks.

92|8|Updated May 15, 2026
One-click install
npx skills add https://github.com/LonelyHerbivore/Trellis-Herbivore --skill trellis-before-dev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: trellis-before-dev
Source: https://github.com/LonelyHerbivore/Trellis-Herbivore/tree/main/.cursor/skills/trellis-before-dev
Command: npx skills add https://github.com/LonelyHerbivore/Trellis-Herbivore --skill trellis-before-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

It prevents developers from starting implementation without first loading the repository’s project-specific coding guidelines, so work stays consistent with existing conventions, pre-development checks, and module-specific spec layers.

Core Features & Use Cases

  • Guideline-first execution: Forces reading prd.md, design.md, and/or implement.md to understand acceptance criteria and implementation intent before any code changes.
  • Spec discovery by package: Uses a package-context mode to determine which .trellis/spec/<package>/<layer> indexes and guideline files apply to the current task.
  • Checklist-driven standards injection: Requires reading the relevant spec index “Pre-Development Checklist” and then opening the listed guideline files, plus always loading shared guides.
  • Use Case: Starting a new coding task (or switching packages) where you need the correct error-handling, conventions, mocks, and other standards applied upfront.

Quick Start

Use trellis-before-dev before writing any code by asking your AI to load the applicable .trellis/spec guidelines for the current package and task artifacts.

Frequently Asked Questions about trellis-before-dev

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I load project-specific coding guidelines before starting AI-assisted development?

To load project-specific coding guidelines before AI-assisted development, you can use a spec-guided workflow that reads your repository's `.trellis/spec` indexes. This ensures your AI understands the correct conventions and pre-development checks before writing any code.

What is spec-guided development and how does it keep code consistent?

Spec-guided development is a workflow approach that forces reading specifications like `prd.md`, `design.md`, and `implement.md` before any code changes. It keeps code consistent by injecting module-specific standards and shared guidelines directly into the AI's context.

How do I apply package-specific error handling and conventions when switching tasks?

To apply package-specific error handling and conventions when switching tasks, you execute a context discovery script that targets the `.trellis/spec/<package>/<layer>` directory. This loads the exact implementation standards required for your current scope.

Does spec-guided development work without a pre-development checklist in the repository?

Spec-guided development relies heavily on a pre-development checklist to function correctly. Without the checklist and relevant spec index files in the `.trellis/spec` directory, the workflow cannot inject the necessary standards and conventions for your task.

How do I ensure my AI coding workflow reads acceptance criteria before implementation?

To ensure your AI coding workflow reads acceptance criteria before implementation, use a guideline-first execution model that parses `prd.md` and `design.md` files. This forces the AI to understand implementation intent prior to making any code changes.