addyosmani--agent-skills
Addy Osmani
e6d4005d1c
Three corrections from review feedback: 1. Drop the `name = "..."` line from all 7 TOML files. The official Gemini CLI custom-command schema only defines `prompt` (required) and `description` (optional) — command names are derived from the filename. The extra key was silently ignored but misleading. 2. Strip the `agent-skills:` prefix from skill references in prompt bodies. That prefix is Claude Code plugin-namespace syntax; Gemini CLI skills are referenced by bare name (e.g., `incremental-implementation`, not `agent-skills:incremental-implementation`). 3. Rewrite ship.toml's Phase A invocation paragraph. The previous text referenced Claude Code's `subagent_type` parameter, which doesn't exist in Gemini CLI. Replace with the actual Gemini CLI model: subagents in `.gemini/agents/` are exposed to the main agent as tools of the same name (also callable via `@persona-name`), and the parallel fan-out works by issuing the three tool calls in a single assistant turn. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
15 行
675 B
TOML
15 行
675 B
TOML
description = "Start spec-driven development — write a structured specification before writing code"
|
|
|
|
prompt = """
|
|
Invoke the spec-driven-development skill.
|
|
|
|
Begin by understanding what the user wants to build. Ask clarifying questions about:
|
|
1. The objective and target users
|
|
2. Core features and acceptance criteria
|
|
3. Tech stack preferences and constraints
|
|
4. Known boundaries (what to always do, ask first about, and never do)
|
|
|
|
Then generate a structured spec covering all six core areas: objective, commands, project structure, code style, testing strategy, and boundaries.
|
|
|
|
Save the spec as SPEC.md in the project root and confirm with the user before proceeding.
|
|
""" |