Turn vague asks into testable scope, success criteria, and a shared plan in one pass
When stakeholders are unclear, change their mind midstream, or deliver non-actionable feedback, this recipe forces clarity fast: goals, success criteria, in-scope/out-of-scope, acceptance criteria, assumptions, and a first-cut plan. It produces a structured kickoff pack you can circulate for sign-off.
Create a skill called "Kickoff Alignment Kit". Goal: turn vague project asks into a signed-off, testable kickoff pack. When I paste a messy brief (notes, emails, or a ticket), you will: 1) Ask only the minimum clarifying questions needed to avoid guessing about scope and success criteria. 2) Produce outputs in this order: - Project Charter-lite (goal, non-goals, constraints, success metrics) - In-scope / Out-of-scope lists - Assumptions + Open Questions register (question, owner, due date) - Deliverables list with acceptance criteria (testable) and definition of done - A 2-week "next steps" plan (milestones, owners, dependencies, risks) 3) Add a "Sign-off request" section with exactly what stakeholders must approve. Guardrails: - Never invent requirements. If information is missing, capture it as an open question. - If methodology is unspecified, keep outputs methodology-neutral. - Use plain language suitable for executives and delivery teams.
Paste a messy project brief — meeting notes, emails, tickets, whatever you have — and this
recipe converts vague statements into measurable outcomes and explicit boundaries. If
information is missing, it captures open questions instead of guessing.
Convert "quick asks" into logged change requests with impact analysis and approvals
Scope creep is a margin killer and a schedule killer. This recipe creates a strict-but-practical change control loop: capture request, classify, analyze impact (time/cost/scope/risk), propose options, and route for approval. It keeps a change log so Slack decisions don't silently rewrite the project.
Change control without the awkward conversation
Converts "quick changes" into structured change requests with phase identification, impact scanning, a revision counter, and a client-ready memo showing time, fee, and schedule impact. Keeps the paper trail clean so you can protect your margins without policing every email.
Replace "post daily" pressure with a repeatable system
Builds a creator workflow designed for consistency: batching, templates, and a content bank. It turns vague advice into an executable weekly plan, so you don't rely on motivation or panic bursts to keep publishing.
Local-first AI assistant that automates small daily tasks safely on your device
A personal, local-first AI assistant that automates small daily tasks—organizing files, setting reminders, and monitoring system events—without touching sensitive data or taking risky actions without your approval.