Write down how work gets done
32 free AI skills and workflows for this job.
- Analysis assumptions logger: Tell it about your analysis. Get every assumption logged with its risk, so reviewers see what could change the answer.
- Analysis write-up builder: Give it your finished analysis. Get a write-up with the question, data, method, results and steps to rerun it.
- Board minutes drafter: Give it a meeting agenda and notes. Get draft board or committee minutes in a proper format. Have a lawyer check them.
- Change request writer: Describe a system or process change. Get a change request with impact, risks, rollback steps and who to tell.
- Clinical report draft checker: Give it de-identified case or trial data. Get a structured report draft and checks for gaps.
- Column mapping document writer: Give it your source and target tables. Get a column-by-column map with rules, gaps and decisions to review.
- Company wiki planner: Describe your business. Get the smallest useful process wiki set-up, with a register of each process.
- Data catalog entry writer: Give it a table and its owner. Get a plain entry with column meanings, quality notes, sources and who may use it.
- Define your metrics once and write a weekly update: Give it your numbers. Get metric definitions, an assumptions log, the weekly update and plain pictures.
- Developer docs writer: Give it your product or draft docs. Get clear developer documentation that follows Google's style guide.
- Documentation system planner: Describe your team and product. Get what to write down, where it lives and how to keep it fresh.
- Employee handbook update agent: Give it each proposed rule change. Get where the rule came from, what it affects and a small test to approve.
- Handover note writer: Paste what you are handing over and to whom. Get a note the next person can run from on day one.
- Lab method validation planner: Name the lab test method and rules. Get a validation plan, acceptance limits and a write-up ready for review.
- Lessons learned note writer: Paste what happened on a finished project. Get a one-page note with what to repeat and what to change.
- Method explainer: Tell it how you did your analysis and who reads it. Get a plain how-we-did-this section with limits.
- Metric definition writer: Tell it how a metric is worked out. Get one agreed definition as checked YAML your team can reuse.
- Monthly developer documentation review: Share your docs and recent changes. Get stale pages fixed, broken steps flagged and a clearer start guide.
- On-call runbook writer: Describe a service or process. Get a step-by-step runbook that anyone on call can follow under pressure.
- Plain-words SQL explainer: Paste a SQL query. Get what it counts, which rows it keeps and what each column means, in plain words.
- Process and SOP writer: Describe how work gets done. Get a flowchart, who does what, and a written procedure with the edge cases.
- Process change note writer: Paste what is changing and why. Get the note that tells the team what to do differently, from when.
- Process documentation update agent: Give it your process docs each month. Get stale or ownerless ones found, rewrite drafts checked and a fix list to approve.
- Repeat task how-to writer: Paste how you do a repeat task. Get exact steps, fixes and who to ask if it fails.
- Repeat task step guide writer: Name a repeat task. Get exact steps, fixes if it fails, how to roll back and who to call.
- Set up a documentation system and write procedures that pass: Give it how your team works. Get a documentation system, procedures, runbooks and a check of each.
- Ship-ready docs writer: Point it at an AI-built app. Get the short set of docs a reviewer needs: architecture, permissions, secrets and test map.
- SOP and runbook checker: Give it your SOPs or wiki export. Get missing owners, stale pages and gaps, plus new SOPs to fix them.
- Status report writer: Give it your project updates. Get a weekly or monthly report with status, risks and decisions needed.
- Weekly status update writer: Paste what got done, what is stuck and what you need. Get a one-page status update.
- Write a procedure, test it and build a training deck: Describe how a job gets done. Get a written procedure, a gap check and a deck to train new people.
- Write docs a new developer can follow on day one: Give it the codebase. Get an architecture read, a README with decisions, a quickstart and a first-run test.