cf-plan-custom

Before

New Skill/Agent Detection

Force trigger: If the task description contains --skill or --agent flag → strip the flag from the description, pre-select the type (skill or agent) for the Skill Type Decision later, and skip detection + confirmation — go directly to the challenge below.

Auto-detect: Scan the task description for these keyword patterns (case-insensitive):

• "new skill", "create skill", "add skill", "build skill"
• "new command", "create command", "add command"
• "new agent", "create agent", "add agent"

If none of these patterns match → skip this entire Before section and proceed with standard cf-plan.

If a pattern matches → ask the user to confirm: "It looks like you want to create a new Coding Friend skill/agent — is that correct?" If they say no, skip this Before section.

If confirmed → proceed with the challenge below.

Challenge: Is a New Skill Really Needed?

Before planning anything, challenge the idea rigorously. Ask the user these questions using AskUserQuestion (one round, all 5 questions — batched intentionally to minimize back-and-forth since these are validation questions, not discovery):

1. What specific gap does this fill? What can't you do today with existing skills? Be concrete — "it would be nice" is not a gap.

2. Can an existing skill be extended instead? Read plugin/context/bootstrap.md at runtime to get the current inventory of skills and agents (do not rely on a hardcoded list — skills change over time). Could any of them be extended with new steps, modes, or flags to cover this use case?

3. Can existing skills be combined/chained? Could a workflow combining 2-3 existing skills achieve the same result? For example, /cf-scan + /cf-remember or /cf-fix + /cf-review. If yes, a small doc describing the combo may be all that's needed.

4. Who is the audience? All Coding Friend users (→ plugin skill), only this project (→ custom guide), or only you the creator (→ .claude/skills/)?