freelance skill
Project Retrospective AI Skill
Turn project notes into a useful retrospective with lessons, risks, wins, and process improvements.
What This Skill Helps You Do
This skill helps you turn scattered context into a reliable retrospective output. It is designed for real work situations where you need a useful first draft, a clear structure, and a way to check whether the result is ready to use.
Best For
- freelancers
- solo founders
- project leads
Use This When
- You have rough notes and need a structured retrospective.
- You want the AI to preserve facts instead of inventing details.
- You need a repeatable template you can reuse for similar work.
Inputs Needed
- project summary
- what went well
- what was hard
- metrics
- next project type
Copy This Skill
Copy This Skill
You are helping me complete this task: retrospective.
Use the context I provide, ask for missing details only if they are essential, and produce a practical output I can use immediately.
Requirements:
- Keep the result specific to my audience and situation.
- Make assumptions visible instead of pretending to know missing facts.
- Use clear headings and concise language.
- Preserve my facts; do not invent experience, claims, prices, or results.
- End with a short quality check and suggested next step.
Input Template
Input Template
Task: retrospective
Audience: [who this is for]
Context: [paste notes, brief, message, resume, reviews, or source material]
Goal: [what a good result should accomplish]
Tone: [plain, warm, direct, polished, friendly]
Constraints: [length, format, must include, must avoid]
Details that must stay accurate: [facts, dates, numbers, names]
Desired next step: [send, revise, publish, review, decide]
Output Format
Output Format
1. Short summary of the task
2. Draft output with clear headings
3. Assumptions or missing context
4. Quality checklist
5. Suggested next step
Example
Example Input and Output
Example input:
Audience: freelancers
Context: I have rough notes and need a usable retrospective by tomorrow.
Goal: Make it clear, specific, and easy to act on.
Tone: Professional but human.
Example output:
A structured retrospective draft with the important facts surfaced first, a concise body, practical next steps, and a short checklist for review before sending or publishing.
Quality Checklist
Quality Checklist
- The output is specific to the audience and task.
- All claims are supported by details you provided.
- The structure makes the next action obvious.
- The tone sounds like something you would actually send or use.
- Missing assumptions are called out clearly.
Fix Bad Outputs
- If the output is too generic, add a real audience, constraints, and one concrete example.
- If the output is too long, ask for a shorter version with the same sections and a tighter word count.
- If the tone is too formal, provide a sample sentence in your own voice and ask the AI to match it.
- If details are missing, paste the missing context and ask the AI to revise only the affected section.
Variations
- ChatGPT: ask it to reason through the checklist before drafting the final answer.
- Claude: give it your examples and ask for a warm, natural tone with clear structure.
- Gemini: include source notes or links when the task depends on current context.
- Codex: use only for work that touches code, technical docs, scripts, or developer workflows.