Sdd Develop

STOP - Read before ANY tool call

1. Read {{GUARDRAILS_PATH}}
2. Read _shared/sdd-artifacts/SESSION.md; load repo session for $Cwd, then after PLAN path is known load develop session scoped by PLAN (or PLAN+step) - see SESSION.md
3. If the relevant gate is not approved: STOP - ask user (pt-BR) - do NOT Write/Shell
4. SDD/develop skills: after ONE step/task, STOP that develop scope - handoff only
5. This skill body is English; user-facing prompts may be (pt-BR)

Step -1 - Gate check (report in chat before continuing)

Gate check:
[ ] guardrails.mdc read
[ ] SESSION.md read; repo + develop (PLAN-scoped) session loaded
[ ] PIPELINE.md read (SDD skills only)
[ ] User confirmed current action (sim)
-> If any unchecked: STOP

Skill: sdd-develop

Trigger

Invoke when the user asks for: /sdd-develop, implement step, execute step.

Outcome

One PLAN step done: code and tests in English; PLAN updated in place. Honor Execution policy in the PLAN (orchestrator mode, child build+tests, receipt/handoff). Do not start the next step in the same develop session scope.

Session scoping: After the PLAN path is resolved, load/create the develop session file per SESSION.md (sessions/{repo-hash}/plan-{plan-hash}.json). When spawned as an O3 parallel child on the same PLAN, use plan-{plan-hash}-step-{N}.json. Gates step_confirmed / tests_run apply only to that scoped file - never share one flat repo JSON across parallel children. Repo session still owns storage_confirmed / write_confirmed.

Language

Do not re-ask SDD storage or change artifact language mid-PLAN unless requested.

Required input

Lazy-load (only when needed)

Never by default: do not preload references/command.md before Step -1 gates; do not preload all dotnet-guidelines/*.md, the full developer-common pack, or all references/*.md. Contract first (PIPELINE + STORAGE); after gates load references/command.md for step discovery; then fan-out on trigger — one references/<section>.md per Process step (SKILL-REFERENCE-RETRIEVAL.md).

Reference routing

Process

After gates: Read references/command.md for ordered step discovery (prefer over dumping this Process into prompts). Then load references/<section>.md for the current step only.

Step -1b - Caveman Mode (Full cap)

1. Read {{SDD_ROOT}}/preferences.json (create { "caveman_mode": false, "caveman_level": "full", "orchestrator_mode": "always", "artifact_language": null } if missing).
2. If caveman_mode is false: continue without compression.
3. If true: load {{TOOLKIT_ROOT}}/skills/_shared/caveman/CAVEMAN.md; apply Full participation cap + prefs caveman_level (Lite skills never escalate); show once: [Caveman] Modo ativo (respostas compactas, level={effective}). Digite caveman off para desativar.
4. Honor caveman on|off|status|lite|full|ultra (and stop caveman / normal mode) during the session.
5. Auto-Clarity + never-compress gates/drafts/paths per CAVEMAN.md.

-1. Pipeline and mode

Load STORAGE.md and PIPELINE.md. Use STORAGE.md schema v2 and run the dynamic storage resolution algorithm with parameter $Workflow = classic. Resolve storage_mode and path for the active repository. If this is the first run for the repository, execute storage mode selection and persist it in manifest.json. Resolve invocation_context per INVOCATION-CONTEXTS.md (IC-DIRECT-ORCHESTRATED): default direct unless O3/parent handoff marks orchestrated. Apply the matching observable table (orchestrated child = one PLAN step; no parent CONTINUITY ownership). Honor CONTRACT-PROVENANCE.md (CP-AGREED-VS-INVENTED): implement Aceite / cited REQs as agreed; new mid-step gaps stay invented until operator confirm — do not silently encode them as requirements. Agent mode is required for code changes and PLAN updates. If the user asks for PRD (sdd-spec) or PLAN (sdd-plan), route using PIPELINE.md section Missing artifacts; do not create PRD/PLAN in this skill.

0. Workspace

Target repo. Resolve PLAN:

Detect stack from PLAN step.

After PLAN path is known: create {sessions}/{repo-hash}/ if needed; load or create develop session with gates false (SESSION.md ┬º Develop session - never copy develop gates from the flat repo JSON). If this child was given an explicit step-scoped path (O3 parallel same PLAN), use plan-{plan-hash}-step-{N}.json.

1. Validate step

Step exists; deps Concluidos / Completed; summarize objective, files, tests, and REQ-NNN / CA targets from step Aceite; ask to proceed.

2. Git

Feature branch per branch-validation.mdc. Read references/git-checklist.md.

3-4. Analyze and implement

Glob/Grep/Read scope. Read references/code-analysis.md and references/stack-pointers.md. Code/tests in English; targeted build/test. When spawned as a child, end with { build, tests, summary } per PLAN Execution policy and SPAWN.md.

4b. Evidence-or-zero (REQ-005 / CA4)

Read references/evidence-or-zero.md. When the step claims AC coverage (or CONTINUITY / operator sets a level ≥ cheap):

1. Create/update features/NNN-slug/EVD/ and features/NNN-slug/STATE.md from templates/features/ (EVD-STATE-CONTRACT.md; detail: references/evidence-or-zero.md).
2. Fill the AC → evidence matrix; levels: off | cheap | standard | strict (default verify = cheap).
3. Run structural gate (deterministic — never LLM-as-validator):

.\scripts\validation\validate-evidence.ps1 -FeatureRoot <features/NNN-slug> [-Level cheap]

Exit ≠ 0 → STOP; do not mark the PLAN step Completed (TE02).

Verifier ≠ O3: evidence verification runs sequentially in this develop session via validate-evidence. Do not use O3 / Task parallelism as the verifier mechanism.

4c. Living loop + TRACE (REQ-006 / CA5)

Read references/living-loop-trace.md. When CONTINUITY / operator closes the feature wave (or the PLAN’s last implement step before P-DOC / archive):

1. Append events to features/NNN-slug/TRACE.jsonl (template: templates/features/TRACE.jsonl; contract: TRACE-ARCHIVE-CONTRACT.md).
2. Run converge → sync current → archive: selective updates to living docs (memory-bank/ / named docs/); do not dump full bank/PRD (SR-NO-FULL-DUMP).
3. Ensure TRACE includes ordered living-loop events converge, sync_current, archive.
4. Run structural gate (deterministic — never LLM-as-validator):

.\scripts\validation\validate-trace.ps1 -FeatureRoot <features/NNN-slug> -RequireArchiveComplete

Exit ≠ 0 → STOP; do not declare archive done. During mid-feature steps, optional trail events may be appended; missing TRACE is OK until archive-complete.

Verifier ≠ O3: archive/TRACE validation is sequential in this session — do not use Task/O3 parallelism as the archive gate.

5. Commit (optional)

Offer /commit; do not auto-commit.

6. Update PLAN + checkpoint

references/plan-update.md: mark step done, progress, next step. Check Aceite items only when the step's cited REQ-NNN / CA are verifiably met. Save before context pause (>=40%).

7. Report

Use references/session-report.md. Files, tests, N/M (pt-BR). Handoff: new chat -> /sdd-develop - <portable-plan-path> - Step N+1.

Must not

Also enforce references/forbidden.md. Before marking Completed: references/quality-self-check.md. Optional user flows: references/optional-flows.md.

• Portuguese application code; multiple PLAN steps per develop session scope (contract unchanged)
• Do not ignore IC-DIRECT-ORCHESTRATED — resolve and apply direct vs orchestrated (INVOCATION-CONTEXTS.md)
• Do not ignore CP-AGREED-VS-INVENTED — do not encode mid-step invented gaps as agreed requirements (CONTRACT-PROVENANCE.md)
• Create PRD/PLAN; skip PLAN save; modify .gitignore
• Implement in Plan/Ask without Agent
• Bypass one-step via orchestrator parent implementing code
• Use the flat {repo-hash}.json for step_confirmed / tests_run when a PLAN path is known - always use the PLAN-scoped file (or PLAN+step); create scoped with gates false if missing
• Write SDD artifacts containing OS absolute paths matching ^[A-Za-z]:/ or user-home InstallRoot embeds (…/.cursor/sdd/…, …/.claude/sdd/…) — use portable paths per STORAGE.md § Portable path
• Mark a step Completed at evidence level ≥ cheap when validate-evidence fails or EVD/STATE are missing
• Use O3 / Task parallelism as the evidence verifier (Verifier ≠ O3)
• Declare archive done when validate-trace -RequireArchiveComplete fails or living-loop events are missing
• Use OpenSpec / .specs/ / SQLite as TRACE or living-spec SoT

Handoff

Example portable path (Classic SDD, repository):

/sdd-develop - features/004-export-profile/US01/PLAN/PLAN_004_export_profile.md - Step 2

(Global: prefix with sdd/<repo-id>/.)