coding-before-dev

name	coding-before-dev
description	Discovers and injects project-specific coding guidelines from .coding/spec/ before implementation begins. Reads spec indexes, pre-development checklists, and shared thinking guides for the target package. Use when starting a new coding task, before writing any code, switching to a different package, or needing to refresh project conventions and standards.

Read the relevant development guidelines before starting your task.

Execute these steps:

1. Read current task artifacts:

   • prd.md for requirements and acceptance criteria
   • design.md if present for technical design
   • implement.md if present for execution order and validation plan

2. Discover packages and their spec layers:

   python3 ./.coding/scripts/get_context.py --mode packages
   

3. Identify which specs apply to your task based on:

   • Which package you're modifying (e.g., cli/, docs-site/)
   • What type of work (backend, frontend, unit-test, docs, etc.)
   • Any spec/research paths referenced by the task artifacts

4. Read the spec index for each relevant module:

   cat .coding/spec/<package>/<layer>/index.md
   

   Follow the "Pre-Development Checklist" section in the index.

5. Read the specific guideline files listed in the Pre-Development Checklist that are relevant to your task. The index is NOT the goal — it points you to the actual guideline files (e.g., error-handling.md, conventions.md, mock-strategies.md). Read those files to understand the coding standards and patterns.

6. Always read shared guides:

   cat .coding/spec/guides/index.md
   

7. Understand the coding standards and patterns you need to follow, then proceed with your development plan.

This step is mandatory before writing any code.