Feature Plan

Prepare a complete contract and small implementation scopes the user can assess separately. Preserve earlier decisions and user instructions; existing material does not require restarting discovery.

Specification

1. Read the input, repository instructions, and code needed to confirm the boundaries of the change. Use the existing document structure.
2. Describe the goal, scope, exclusions, state ownership, shared contracts, and meaningful failure behavior. Include migration, deployment, and rollback when relevant. Match detail to the risk and complexity.
3. Separate accepted decisions from recommendations and unknowns. Present the main choices and their consequences. Earlier acceptance of the recommended set is sufficient; silence is not acceptance.
4. Distinguish design decisions from execution prerequisites, such as environment availability. An open issue blocks only stages whose scope or credible verification depends on it. Prepare the remaining design for review.