Pm Spec From Code

Goal

• Produce a product-behavior spec based on the implemented code.
• Prefer short, declarative rule sentences over long explanations.

Output Format

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>

Writing Rules

• Put exactly one rule in each bullet.
• End each bullet with a single sentence.
• Avoid vague wording such as "appropriately," "flexibly," or "when possible."