developer-notes-protocol
Installation
SKILL.md
Developer Notes Protocol — SACRED LAW
Purpose
Developer Notes are the single highest-priority input in the entire pipeline. They represent direct, authoritative instructions from the developer who owns the feature. Every word must be followed exactly — without interpretation, override, or exception.
Dual Mode — One Skill, Two Consumers
This skill is shared. Do not create a coding-specific duplicate.
| Mode | Invoked By | Responsibility |
|---|---|---|
| Extraction | Analysis Agent — Phase 1 | Scan the JIRA story, extract notes verbatim, assign DN-001, DN-002 …, keep the list active through Phases 2–9 |
| Enforcement | Coding Orchestrator — Phase 2 | Consume the numbered DN table from ANALYSIS_PLAN.md Section 1, apply each note as the highest-priority constraint during generation, and attach file-level evidence |
Preserve IDs across modes. A note numbered DN-002 during analysis remains DN-002 for the whole life of the story — through code generation and into the final summary. Never renumber.