sdd или sdlc-skills

Spec-Driven Development pipeline: 23 atomic Socratic skills (survey/scaffold → spec → ux-flows → design → data-model → api → screens → tasks → tests → implement → review → ship) + a living decomposition roadmap (steps + dependency graph + parallel-safe execution waves) above the per-feature flow + 10 subagents, plus a TDD implementation engine with agent-team and dynamic-workflow modes. The Q&A skills are depth-tunable (easy/medium/hard); the ideation analyses (researcher/strategist/analyst/devil's-advocate) run as named subagents gated by that dial; diagrams are confirmed in prose; and every acceptance criterion is covered end-to-end. Surface-aware: declare target surfaces at design (backend/web/mobile/desktop/CLI/worker/library, as C4 containers); downstream gates the `ui` task layer, UI-driven flows, and frontend test tiers. UI features get a design pipeline (auto-skipped for backend-only work): design-system (the committed canon — Figma MCP / Pencil MCP / code-markdown; on pencil it also bootstraps and se

Ten battle-tested SDLC skills: sdlc-intent (PRD digest + seven-layer audit + A/B/C risk tiering), sdlc-design (technical design: alternatives, tiered interface contracts, shared assets, C/H decisions, slicing constraints), sdlc-test (cases/dev/static/exec/spec/report with human checkpoints), sdlc-gate (risk-tiered adversarial review gate: 4/2 fresh-context subagents or self-check, plus guard_dev), sdlc-doubt (adversarial re-check of non-trivial decisions), sdlc-ui-visual (design-to-code visual restoration via screenshots: DOM geometry + pixel heatmap + tiered fix rounds), sdlc-release-check (pre-release audit: config keys, job/MQ registrations, DDL/DML grading, runbook), sdlc-guardrails (write-time red-line engine: PostToolUse hook + pre-commit + baseline scan), sdlc-sync (artifact sync bridge between local markdown and the team-facing platform), sdlc-handoff (cross-agent session handoff: self-contained card, drift check, direct takeover).