851 B
851 B
name, description
| name | description |
|---|---|
| ticket-analysis | 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:
- Summary
- Confirmed requirements
- Existing behavior and affected DDR evidence
- Open questions and assumptions
- Suggested implementation steps
- Risks and regression impact
- 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.