Sdd MCP

Generate STATUS.md from the current project specs and logbook.

Install the compact spec/ sidecar into an EXISTING external project directory (the recommended layout for real projects outside this template), via scripts/install-spec-sidecar.sh. After this, every other tool works against that projectRoot. Refuses the template root, like every tool here.

Scan an existing codebase for route/API and user-flow signals and write analysis/legacy-discovery/ (evidence files + report with suggested first specs). TypeScript port of scripts/legacy-discovery.sh — no bash, no ripgrep needed. The entry point for adapting a project that already has code (Case 2 of the guides).

Lint acceptance criteria against the EARS skeleton (CUANDO/SI/MIENTRAS … EL SISTEMA DEBERÁ … / WHEN/IF/WHILE … THE SYSTEM SHALL …) plus vague-word checks. Pure and advisory — the same validateEarsCriterion the Builder uses; results are suggestions, never blockers. No filesystem access.

List numbered specs and their approval status.

Swap one task with the nearest task above/below it in tasks.md, skipping non-task lines (atomic write). 'Move to the end' is repeated 'down'. Returns the updated task list with line numbers.

Claim the oldest pending AI-assist request published by the SDD Builder (pending -> in_progress) and return it with its full context: target field, its current text, and the user's instruction. Returns { request: null } when the queue is empty — polling also records agent presence, which is what the builder shows as 'agent connected'. Answer with sdd_respond_request; never write the spec files yourself.

Read the project logbook: without fileName, list the markdown files of one bitácora folder (handoffs, decisiones, diaria, global — sorted, so the last one is the latest); with fileName, return that file's content. The read counterpart of sdd_write_handoff/sdd_write_decision/sdd_write_daily_log/sdd_append_project_log.

Read one document of a numbered spec bundle (spec.md, plan.md, tasks.md, research.md or history.md) as raw markdown. The read counterpart of sdd_approve_spec/sdd_update_spec_sections, for agents without filesystem access (HTTP/Desk).

Read the checkbox tasks of a spec's tasks.md with their line numbers and done state.

Record explicit user consent before implementation starts. Pass specId so the consent is bound to that spec; without it the entry is a legacy, markerless line that only covers specs approved before it.

Delete one task checkbox line from tasks.md; every other line survives byte for byte (atomic write). Returns the updated task list with line numbers.

Replace the text of one task checkbox line in tasks.md, preserving its indentation and done mark (atomic write, same primitive as sdd_set_task_done). Returns the updated task list with line numbers.

Attach a proposal to a claimed AI-assist request (in_progress -> answered). The proposal is plain text for the target field; for structure-idea and review-spec requests it is exactly the JSON the instruction asks for, with no markdown around it. A review-spec answer is a list of findings anchored to the spec sections — findings, never a rewritten spec. It is NOT written to any spec file: the user reviews it in the builder and only their acceptance writes, through the existing section/task routes.

Score a spec bundle 0-100 with grade (A/B/C/D) and improvement notes: required files present, spec sections, plan signals (milestones/dependencies/risks), task breakdown, research rationale, dated history. One spec (specId) or every spec (omitted). Heuristics-parity port of scripts/score-spec.sh.

Toggle one checkbox line in a spec's tasks.md (surgical edit, atomic write) and return the updated tasks.

Replace ONLY the content under the guided-editor headings of a spec.md (user story, acceptance scenarios, EARS criteria, requirements, spec properties, success criteria, out of scope — the full template) preserving everything else, the approval block included. Tolerant to the EN/ES headings of the canonical repo template (specs/_template/spec.md).

Update the status, priority and/or owner cells of ONE spec's row in specs/INDEX.md (and refresh its updated date). The only write INDEX accepts besides appending a new row — until now a status change meant editing the table by hand. Fails when the spec has no row.

Bring an installed SDD sidecar up to the version of this server. Framework-owned files (the gate, validators, root resolver) are repaired; files the user owns (sdd.policy.yaml, specs/_template/*, logbook templates) are NEVER written unless named in applyPreserved. Call with dryRun: true first — it reports what would change and writes nothing. An already-current sidecar performs zero writes.

Validate the SDD structure and required files of a project.

Create or replace a daily log entry in bitacora/diaria.

Create or replace a decision file in bitacora/decisiones.

Create or replace a handoff file in bitacora/handoffs.

Write the FULL content of one spec bundle document (spec.md, plan.md, tasks.md, research.md or history.md), atomically. The low-level counterpart of sdd_read_spec_document; prefer sdd_update_spec_sections for structured edits of spec.md. Any name outside the five fails without touching the filesystem.