Translate user intent into a SpecD change plan with exploration context.
npx skills add https://github.com/specd-sdd/SpecD --skill specd-new
Please help me install this Agent Skill. Skill: specd-new Source: https://github.com/specd-sdd/SpecD/tree/main/.gemini/skills/specd-new Command: npx skills add https://github.com/specd-sdd/SpecD --skill specd-new
The specd-new skill enables teams to translate ambiguous user intent into a structured SpecD change plan, surfacing relevant specs and capturing exploration context before any artifact is written.
Load the project context and begin intent discovery for a new SpecD change.
High-intent search queries and answers about installing and using this skill.
You can translate user intent into a structured change plan by running a discovery session to surface affected specs, propose a change scope, and capture exploration context without writing artifacts.
A SpecD change discovery workflow loads project context, registers specs, runs entry and exit hooks, and saves exploration state to support downstream design steps.
You identify affected specs by loading project context and inspecting workspaces during intent discovery, which surfaces relevant specifications for the proposed change scope.
No, the discovery process does not produce artifacts. It solely saves a comprehensive exploration record in a .specd-exploration.md file to support subsequent design steps.
Yes, you can save exploration context by writing a .specd-exploration.md file that captures the discovery session details while strictly enforcing guardrails against generating artifacts.
You should not use a discovery session when you need to directly produce design artifacts or code, as this workflow specifically captures exploration state without generating output files.
pradeepmouliGenerate baseline-spec.md and current-state.md from repository analysis.
specd-sddImplement SpecD change tasks across workspaces with guardrails and hooks.
magicpro97Generate Copilot CLI preToolUse and postToolUse hooks with templates.
matchojeckiAudit specification backward-compatibility risks and gaps for pre-implementation analysis.
