Assess

Use this skill after add-subfeature when an existing canonical feature has a selected durable subfeature and you need explicit impact assessment before subfeature-local design begins.

Read these references when relevant:

• references/config-surface-governance.md when the subfeature touches configuration, startup, compatibility boundaries, environment injection, or test harness inputs

Responsibilities

1. Resolve the target parent feature and selected subfeature.
2. Inspect parent planning artifacts under docs/features/<feature-slug>/.
3. Identify affected baseline artifacts, story IDs, planned slice IDs, and increment IDs.
4. Capture inherited constraints, especially existing ownership of configuration and state surfaces that the subfeature should reuse.
5. Write impact-analysis.md inside the selected subfeature folder.
6. Synchronize the discovered impact lists back into .subfeature-meta.json.