feature-delivery
Feature delivery evidence
Read repository instructions and apply session-delivery-hygiene. This skill does not authorize publication, new dependencies, or unrelated changes. Use proportionate evidence; do not turn a small fix into a repository-wide audit.
1. Start and maintain the decision record
For every new feature, extend its existing design document/RFC or create
docs/decisions/<feature-name>.md. Keep it versioned with the implementation
and link it from the PR so the reasoning survives the session. Do not create
duplicate records; non-feature fixes can use existing issue/PR rationale.
Keep temporary logs and captures in task-owned artifact storage, not in source
control; preserve concise findings and accessible evidence references in the
record. Do not include secrets, personal data, or public vulnerability details.