Results for “work-in-progress”

3 skills

Compress the entire current conversation into a clean, structured handoff document that lets a new chat session, a colleague, or future-you resume the work without losing decisions, constraints, or progress. Use this skill whenever the user says "handoff", asks to summarize the thread to continue elsewhere, mentions hitting context limits or the chat getting too long, wants to brief a teammate on this conversation, or asks to export or save where things stand. ALSO offer it proactively when a long working thread is clearly winding down or the user says they'll "pick this up later". Do NOT use for summarizing external documents or meetings; this skill summarizes the conversation itself.

More results

Jobs To Be Done

Use to CREATE or REVIEW a Job to be Done (JTBD) in Alan Klement's demand-side, progress-based sense — a job is the progress a customer is trying to make, never a task or feature. Trigger whenever someone wants to write or draft a JTBD, job statement, or job story; figure out the real motivation, struggle, or progress behind a feature, request, or product; understand why customers switch, adopt, or churn; turn interview notes or research into jobs; or pressure-test, sharpen, or rewrite existing JTBDs into proper jobs. Also trigger on "grill my JTBD", "is this a real job or just a task/feature", "what's the actual job here", "why would they switch". In an A-Team target repo, jobs are durable artifacts — this skill writes docs/product/jtbd/NN-<slug>.md per CONTRACT.md and never deletes or silently rewrites a job. Do NOT use for writing PRDs, roadmaps, tickets, or acceptance criteria (those consume a finished JTBD), or for implementation user stories.

Summarize AFPS product-workflow progress from existing artifacts and recommend the next concrete skill command