Paadhai Skill

This confirms we are in a Paadhai-managed project.

STEP 2 — Gather Skill Info

Ask user:

1. Skill name — kebab-case (e.g., dev-foo, project-bar)
2. Trigger description — "Use when..." (what condition activates this skill)
3. Purpose — one sentence describing what the skill does
4. Modifies code? — yes/no (determines whether gates are needed)
5. Pipeline position — after which existing skill? or standalone utility?

Validate:

• Name must be kebab-case, no spaces, no uppercase
• Name must not conflict with existing skills
• Trigger description must start with "Use when"

STEP 3 — Read Conventions

[READ] references/claude-tools.md — load capability marker mappings.

[READ] one existing skill as reference template (e.g., .claude/skills/dev-start/SKILL.md).

[READ] CLAUDE.md — current skill table (to find correct insertion point).

[READ] .claude-plugin/plugin.json — current skill registry.

STEP 4 — Determine Next Gate Number

[SHELL] Find the highest gate number in use:

grep -roh "G-[0-9]*" .claude/skills/ | sort -t- -k2 -n | tail -1

Next gate = highest + 1. If skill does not modify code (from Step 2), no gate is needed.

STEP 5 — Generate Skill Scaffold

Build the SKILL.md content following all Paadhai conventions:

---