trellis-before-dev

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.