Menú
Use when starting a new session to understand how superspec skills work and when to invoke them
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
Use before creating features, building components, adding functionality, or modifying behavior to explore user intent, requirements, and design before implementation
Use when you have a spec or requirements for a multi-step task, before touching code
Use when a change packet's implementation is complete and you want to promote it into the project's permanent spec layout before closing the change out. Typical trigger phrases include "archive this change", "we're done with change X", or invocation after ss-executing-plans / ss-subagent-driven-development report all tasks complete.
Use when a non-engineer (PM / designer / product owner) has opened a frontend PR sketching a new feature's UI and user-flow with mocked data or stubbed API calls, and engineering needs to extract requirements, reason about backend / API support, and produce an OpenSpec change directory ready for ss-writing-plans
Use when executing implementation plans with independent tasks in the current session
| name | ss-using-superspec |
| description | Use when starting a new session to understand how superspec skills work and when to invoke them |
Superspec skills override default system prompt behavior, but user instructions always take precedence:
If CLAUDE.md says "don't use TDD" and a skill says "always use TDD," follow the user's instructions.
Use the Skill tool. When you invoke a skill, its content is loaded and presented to you — follow it directly. Never use the Read tool on skill files.
Invoke relevant skills BEFORE any response or action. If a skill clearly applies to what you're about to do, invoke it first.
digraph skill_flow {
"User message received" [shape=doublecircle];
"Skill applies?" [shape=diamond];
"Invoke Skill tool" [shape=box];
"Announce: 'Using [skill] to [purpose]'" [shape=box];
"Follow skill" [shape=box];
"Respond" [shape=doublecircle];
"User message received" -> "Skill applies?";
"Skill applies?" -> "Invoke Skill tool" [label="yes"];
"Skill applies?" -> "Respond" [label="no"];
"Invoke Skill tool" -> "Announce: 'Using [skill] to [purpose]'";
"Announce: 'Using [skill] to [purpose]'" -> "Follow skill";
}
When multiple skills could apply, use this order:
"Let's build X" → ss-brainstorming first, then implementation skills.
Superspec skills do NOT execute git write commands (commit, push, merge, rebase, branch delete). The user handles their own git workflow. Read-only git commands (status, log, diff) are fine for gathering information.