trellis-before-dev

Read .trellis/spec indexes and checklists to apply project coding guidelines before implementation.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/jhxxr/OpenSciReader --skill trellis-before-dev-jhxxr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: trellis-before-dev
Source: https://github.com/jhxxr/OpenSciReader/tree/main/.opencode/skills/trellis-before-dev
Command: npx skills add https://github.com/jhxxr/OpenSciReader --skill trellis-before-dev-jhxxr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Discovers and applies project-specific coding guidelines from .trellis/spec/ before implementation begins. This ensures new tasks start with a consistent standard across packages.

Core Features & Use Cases

  • Read and map .trellis/spec indexes and Pre-Development Checklists to the current task.
  • Read the specific guideline files linked by the Pre-Development Checklist (e.g., error-handling.md, conventions.md, mock-strategies.md) to enforce project standards.
  • Read shared guides in .trellis/spec/guides to align with organizational best practices.

Quick Start

Run the pre-development plan by listing relevant packages and applying the applicable specs using the trellis tooling.

Frequently Asked Questions about trellis-before-dev

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

FAQPage Schema
How do I apply project-specific coding guidelines before starting development?

To apply project-specific coding guidelines before development, this Skill reads spec indexes and Pre-Development Checklists from the .trellis/spec/ directory to inject relevant standards into your current task.

What are pre-development checklists and how do they enforce coding conventions?

Pre-Development Checklists map project-specific standards to your current task by linking to individual guideline files like error-handling.md and conventions.md, ensuring consistent coding conventions across all packages.

How do I ensure consistent coding standards across multiple packages in a monorepo?

You ensure consistent coding standards across multiple packages by reading shared thinking guides in .trellis/spec/guides and applying organizational best practices discovered through the trellis spec index before implementation begins.

Can I use this to inject error handling and mock strategies before writing code?

Yes, you can inject error handling and mock strategies before writing code by inspecting individual guideline files such as error-handling.md and mock-strategies.md linked within the .trellis/spec/ directory structure.

Do I need a .trellis/spec/ directory to run the pre-development workflow?

Yes, you need a .trellis/spec/ directory containing spec indexes, Pre-Development Checklists, and guide files to run the pre-development workflow and establish project coding standards.

What is the best way to discover organizational best practices before coding a new feature?

The best way to discover organizational best practices before coding is reading shared guides within .trellis/spec/guides and mapping applicable specs from the trellis index to align with project requirements.