trellis-before-dev

To inject project-specific coding guidelines, the Skill discovers and reads spec indexes from the .trellis/spec/ directory, retrieving Pre-Development Checklists and shared thinking guides to establish coding standards before you begin coding.

Pre-development checklists are needed when starting a new coding task, switching to a different package, or refreshing project conventions to ensure your implementation aligns with target package standards and avoids rework.

Yes, you can use this to align coding tasks with project conventions across different packages by reading the spec indexes for the relevant packages and injecting those specific guidelines into your task context.

The best way to enforce coding standards before coding begins is by reading the guideline files listed in the Pre-Development Checklist and shared guides located in the .trellis/spec/ directory, establishing conventions early.

Your implementation deviates from target package standards if project-specific coding guidelines from the .trellis/spec/ directory are not discovered and injected into the task context before development begins, leading to potential rework.

Yes, trellis-before-dev supports onboarding by retrieving Pre-Development Checklists and shared thinking guides from .trellis/spec/, injecting project-specific guidelines into the task context to guide implementation and team onboarding.