33 lines
1.8 KiB
Markdown
33 lines
1.8 KiB
Markdown
---
|
|
name: ticket-delivery
|
|
description: Prepare a concise project-manager reply and billable work report for reviewed FileMaker ticket work. Use when summarizing completed or reviewed work for a client, project manager, invoice, or handoff.
|
|
---
|
|
|
|
# FileMaker Ticket Delivery
|
|
|
|
## Preconditions
|
|
|
|
- Read the current ticket, relevant confirmed decisions, and the project's delivery rules.
|
|
- For early analysis, label the response as a draft or return only the questions needed to continue.
|
|
- Do not describe a proposal, an unverified assumption, or an open dependency as completed implementation.
|
|
- Never send, post, or otherwise deliver the reply unless explicitly asked.
|
|
|
|
## Project-manager reply
|
|
|
|
- Lead with completed work, followed only by unresolved questions or confirmations needed.
|
|
- Use concise, practical, client-facing English. Remove internal exploration and unused architecture proposals.
|
|
- Distinguish completed work from proposed next steps.
|
|
- When useful for verification, give a friendly label followed by the exact FileMaker object name in brackets, for example `Utility Switch [APPROVE::UtilitySwitch]`.
|
|
- Include exact layout, script, custom function, or value-list names only when they materially help verification.
|
|
- Include FileMaker code only when a calculation or script rule is central to approval. Put it at the end under a concise `KEY CALCULATIONS` or `KEY SCRIPT LOGIC` heading.
|
|
|
|
## Short work report
|
|
|
|
Create one only when the project requires it or the user requests it.
|
|
|
|
- Maximum 450 characters, including title, bullets, and line breaks.
|
|
- Start with the ticket number and a short title.
|
|
- Use one to three short past-tense bullets describing completed work.
|
|
- Exclude code, open questions, testing instructions, and unconfirmed claims.
|
|
- Put the report in a fenced `text` block so it is easy to copy.
|