superspec

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

Use when starting a new session to understand how superspec skills work and when to invoke them