Convert implemented code into a PM-style spec focused on user-visible behavior and rules. Use when the user wants a feature spec derived from code, with behaviors, rules, constraints, exceptions, and non-goals in product language. Do not use for API documentation, code comments, or architecture documentation.
Write the result in Markdown using this structure.
# <Feature Name> Spec
## Purpose
- <The user problem this feature solves>
## Core Behavior
- <User-visible behavior 1>
- <User-visible behavior 2>
## Detailed Rules
- <A rule in condition -> outcome form>
- <Priority or conflict-resolution rule>
## Constraints And Exceptions
- <Minimum / maximum / disallowed condition>
- <Boundary-case handling>
## Non-goals
- <Scope not covered by this feature>
## Open Questions
- <Policy question that cannot be confirmed from code alone>
Open Questions.Request: Create a spec for the table resize feature
Rule sentence examples: