27 lines
851 B
Markdown
27 lines
851 B
Markdown
---
|
|
name: ticket-analysis
|
|
description: Analyze a FileMaker ticket into confirmed requirements, questions, affected existing behavior, implementation steps, risks, and tests without inventing business rules.
|
|
---
|
|
|
|
# Ticket Analysis
|
|
|
|
Use this skill before proposing implementation for a ticket, email request, or developer handoff.
|
|
|
|
## Output
|
|
|
|
Return only the sections needed by the project, normally:
|
|
|
|
1. Summary
|
|
2. Confirmed requirements
|
|
3. Existing behavior and affected DDR evidence
|
|
4. Open questions and assumptions
|
|
5. Suggested implementation steps
|
|
6. Risks and regression impact
|
|
7. Test cases
|
|
|
|
## Rules
|
|
|
|
- A client decision is not confirmed merely because it appears in a draft or an old ticket.
|
|
- Ask short, decision-oriented questions instead of filling gaps with guesses.
|
|
- Keep a proposed design distinct from verified current implementation.
|