trellis-before-dev

To check project coding guidelines before development, you need a pre-development checklist that reviews requirements, design, and execution plans against project-specific specifications to ensure compliance with established standards.

Pre-development specification reviews are processes that verify adherence to project-specific coding conventions. You need them when starting new coding tasks, switching packages, or refreshing your understanding of project standards to maintain code compliance.

Reading spec index files involves accessing and interpreting guideline files within a designated project directory. This ensures you understand and agree to follow the shared guides covering coding standards and best practices before writing code.

Yes, reviewing pre-development checklists and specs requires a specific directory containing spec/index files and shared guides. This structure allows the system to access and interpret project-specific coding guidelines for compliance.

The best way to ensure adherence when switching packages is to run a pre-development review process that accesses spec indexes and shared guides. This verifies your understanding of the new package's coding conventions before you begin work.

Pre-development guideline reviews fail to find project standards when the required directory containing spec/index files and shared guides is missing. Without these specification files, the system cannot access or interpret the project's coding conventions.