idea-generatorlisted

# Skill Creator — AI-PM Operator Create new skills or improve existing ones. Every skill you create joins a toolkit used daily by the Product engineering team — it must be practical, well-integrated, and follow AI-PM Operator conventions. ## Step 0: Bootstrap Read silently (don't announce): 1. `team.json` — team roster, domains, aliases 2. `CLAUDE.md` — non-negotiable rules, key references 3. List `.claude/skills/` — know what already exists (avoid duplicates/overlaps) Parse `$ARGUMENTS`: - If a skill name is given → check if it exists under `.claude/skills/{name}/` - If `--improve` → load existing SKILL.md, enter improvement mode (Step 4) - If `--from-conversation` → extract the workflow from conversation history - If no args → interactive creation mode (Step 1) --- ## Step 1: Capture Intent Understand what the skill should do before writing anything. If the conversation already contains a workflow the user wants to capture (e.g., "turn this into a skill"), extract answers from context first — tools used, steps taken, corrections made, input/output formats observed. Ask the user to confirm or fill gaps on these questions: 1. **What does this skill do?** (one sentence) 2. **Archetype**: Is it an **Expert/Advisor** (loads knowledge, answers questions) or a **Task Executor** (runs a workflow, produces output)? 3. **When should it trigger?** (what would someone type to invoke it?) 4. **What inputs does it need?** (Jira key? PR number? free text? flags?) 5. **What does i