1.3 KiB
1.3 KiB
name, description
| name | description |
|---|---|
| trellis-before-dev | Load the task and affected-layer guidelines before implementation or when scope changes. Not for pure consultation or repeated reading of unchanged context. |
Before Development
- Read the current PRD and applicable design/implementation notes if not already current in context.
- Identify the smallest behavior gap, affected files, exclusions and validation commands. Reuse the approved plan rather than writing another checklist.
- Discover package indexes only when the affected layer is unknown. Read its relevant coding and quality contracts; follow references needed for this change.
- Read cross-layer or reuse guides only when shared contracts, multiple layers, shared constants or new abstractions are involved.
- Once the plan is approved, continue through implementation and relevant validation. Ask again only for material changes to scope, risk or acceptance, or separately protected operations.
- Keep unrelated dirty files and pre-existing failures out of scope. A local refactor requires evidence that behavior stays unchanged.
Do not force full document reads, repeat unchanged context, require unavailable tools, or turn a rule-only task into full business testing. Preserve privacy, production and independent-review boundaries from AGENTS.md.