sdd-patch

Generates a combined explore, propose, and spec artifact for trivial SDD changes.

Updated Apr 4, 2026
One-click install
npx skills add https://github.com/juanjo-zurich/juarvis-v4 --skill sdd-patch-juanjo-zurich
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sdd-patch
Source: https://github.com/juanjo-zurich/juarvis-v4/tree/main/plugins/sdd/skills/sdd-patch
Command: npx skills add https://github.com/juanjo-zurich/juarvis-v4 --skill sdd-patch-juanjo-zurich

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Running the full Spec-Driven Development cycle (explore, propose, spec) is excessive for trivial changes like hotfixes, typos, or minor configuration edits. This Skill fuses those three phases into a single lightweight markdown artifact so small changes stay documented without the overhead of the complete workflow. ## Core Features & Use Cases - Fused SDD Phases: Produces one markdown artifact with clearly separated Exploration, Proposal, and Specification sections, including functional requirements and acceptance scenarios. - Complexity Guardrails: Evaluates eligibility criteria (3 files or fewer, no architectural changes) and emits a visible warning recommending the standard flow when the change is too complex. - Orchestrator Integration: Returns a structured envelope so the orchestrator can decompose the artifact into three Engram observations (explore, proposal, spec) with standard topic keys, supporting engram, openspec, hybrid, and none storage modes. - Use Case: A developer needs to fix a typo in a config file. Instead of running three separate SDD phases, the orchestrator launches this patch mode to produce one concise artifact documenting the current state, the proposed fix, and acceptance criteria. ## Quick Start Ask the orchestrator to run /sdd-new my-hotfix --patch to generate a combined explore, propose, and spec artifact for a trivial change.

Frequently Asked Questions about sdd-patch

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a quick SDD spec for a small hotfix?▼

Use patch mode by launching the orchestrator with /sdd-new <change> --patch. It fuses the explore, propose, and spec phases into one markdown artifact with three separated sections, avoiding the overhead of the full SDD cycle.

When should I use patch mode instead of the full SDD workflow?▼

Use patch mode only for trivial changes: hotfixes, typos, or minor configuration edits affecting three or fewer files with no architectural impact. Anything more complex should use the standard /sdd-new flow, and the skill emits a warning when thresholds are exceeded.

Does the patch skill save artifacts directly to Engram?▼

No, the skill never persists artifacts itself. It returns the combined content to the orchestrator, which decomposes it into three separate Engram observations using the standard topic keys for explore, proposal, and spec.

What storage modes does the SDD patch workflow support?▼

It supports four persistence modes: engram, openspec, hybrid, and none. The mode is resolved through the shared persistence contract, and hybrid mode applies both the engram and openspec conventions simultaneously.

What happens if my change is too complex for patch mode?▼

The skill still generates the artifact but includes a visible warning stating the change exceeds patch eligibility, such as affecting more than three files or having architectural impact, and recommends using the standard /sdd-new flow instead.