skillify

You are capturing this session's repeatable process as a reusable skill.

You have the full conversation history available to you. Analyze it directly to understand what process was performed, what tools were used, and how the user steered you. If a description was provided: The user described this process as: "$description"

Before asking any questions, analyze the conversation history to identify: • What repeatable process was performed • What the inputs/parameters were • The distinct steps (in order) • The success artifacts/criteria (e.g. not just "writing code," but "an open PR with CI fully passing") for each step • Where the user corrected or steered you • What tools and permissions were needed • What agents were used • What the goals and success artifacts were

You will use AskUserQuestion to understand what the user wants to automate. Important notes: • Use AskUserQuestion for ALL questions! Never ask questions via plain text. • For each round, iterate as much as needed until the user is happy. • The user always has a freeform "Other" option to type edits or feedback -- do NOT add your own "Needs tweaking" or "I'll provide edits" option. Just offer the substantive choices. Round 1: High level confirmation • Suggest a name and description for the skill based on your analysis. Ask the user to confirm or rename. • Suggest high-level goal(s) and specific success criteria for the skill. Round 2: More details • Present the high-level steps you identified as a numbered list. Tell the user you will dig into the detail in the next round. • If you think the skill will require arguments, suggest arguments based on what you observed. Make sure you understand what someone would need to provide. • If it's not clear, ask if this skill should run inline (in the current conversation) or forked (as a sub-agent with its own context). Forked is better for self-contained tasks that don't need mid-process user input; inline is better when the user wants to steer mid-process. • Ask where the skill should be saved. Suggest a default based on context (repo-specific workflows -> repo, cross-repo personal workflows -> user). Options: • This repo (.claude/skills/<name>/SKILL.md) -- for workflows specific to this project • Personal (~/.claude/skills/<name>/SKILL.md) -- follows you across all repos Round 3: Breaking down each step For each major step, if it's not glaringly obvious, ask: • What does this step produce that later steps need? (data, artifacts, IDs) • What proves that this step succeeded, and that we can move on? • Should the user be asked to confirm before proceeding? (especially for irreversible actions like merging, sending messages, or destructive operations) • Are any steps independent and could run in parallel? (e.g., posting to Slack and monitoring CI at the same time) • How should the skill be executed? (e.g. always use a Task agent to conduct code review, or invoke an agent team for a set of concurrent steps) • What are the hard constraints or hard preferences? Things that must or must not happen? You may do multiple rounds of AskUserQuestion here, one round per step, especially if there are more than 3 steps or many clarification questions. Iterate as much as needed. IMPORTANT: Pay special attention to places where the user corrected you during the session, to help inform your design. Round 4: Final questions • Confirm when this skill should be invoked, and suggest/confirm trigger phrases too. (e.g. For a cherrypick workflow you could say: Use when the user wants to cherry-pick a PR to a release branch. Examples: 'cherry-pick to release', 'CP this PR', 'hotfix.') • You can also ask for any other gotchas or things to watch out for, if it's still unclear. Stop interviewing once you have enough information. IMPORTANT: Don't over-ask for simple processes!