Menú
Restore working context from `.project/PLAN.md` (and a fresh handoff, if any), and apply any configured modes.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
Design a target architecture for a new system — module boundaries, dependency rules, seams, and build order — from its requirements. Reports a blueprint; changes nothing.
Analyze an existing codebase's architecture and produce a sequenced refactoring plan — assess module boundaries, dependency structure, and layering, then lay out ordered, risk-tagged steps. Language-agnostic. Reports a plan; changes nothing.
Turn a goal or another command's output into an ordered task roadmap.
Find the root cause of a failure with the scientific method — reproduce, isolate, fix, then prove it.
Interview the user relentlessly about a plan or design until reaching shared understanding.
Run an extremely strict maintainability + single-source-of-truth review of code changes — abstraction quality, file sprawl, spaghetti-condition growth, and duplicate/competing implementations. Reports findings by default; `--fix` applies the mechanical, unambiguous ones — structural/code-judo restructurings rest on judgment and stay reported.
| name | ds-project-resume |
| description | Restore working context from `.project/PLAN.md` (and a fresh handoff, if any), and apply any configured modes. |
| disable-model-invocation | true |
When invoked, read the project's persisted state and report where to pick up — the counterpart to /ds-project-checkpoint. Safe to run at the start of any session.
--no-modes — skip applying the modes in .project/config.md. Resume still lists what the project configures, so opting out never hides them.--no-modes). If .project/config.md exists, read its ## Modes list and, for each mode, read that mode's installed skill file — <name>/SKILL.md under your assistant's skills directory (~/.claude/skills/, $CLAUDE_CONFIG_DIR/skills/, ~/.codex/skills/, ~/.config/opencode/skills/) — and adopt its rules for the rest of the session (read-and-adopt). Echo which modes you applied; for a mode that grants an authorization or destructive-ish behavior — e.g. ds-git-mode's standing authorization to commit without asking — spell out that consequence in the echo so it is never a surprise. If a listed mode can't be found, say so and tell the user to apply it manually — never silently skip. With --no-modes, don't apply them but still list what config.md configures. If .project/config.md is absent, drop a one-line hint that the user can create one with /ds-project-config to auto-apply modes..project/PLAN.md does not exist, say so and suggest /ds-project-map then /ds-roadmap. Stop..project/PLAN.md — focus on ## Now (state, next, open questions) and the ## Roadmap status..project/PROJECT.md if present, for the repo map and constraints..project/DECISIONS.md if present — note how many decisions it records and surface the most recent few if they bear on the next action. Never dump the whole file; it grows over time..project/handoff.md exists, check whether it is still current — by file modification time, not git (the workflow must work when .project/ is git-ignored or the repo has no git):
handoff.md is newer than .project/PLAN.md, load it — it's the freshest context.PLAN.md (a checkpoint happened after it), treat it as stale: mention it exists and its date, but do not rely on it..project/ files — it reads them. Applying a configured mode is part of resume; once applied, that mode governs the session under its own rules.SKILL.md.## Now over a stale handoff.md.A short orientation — where we are, the next step, open questions, and which modes were applied (or skipped) — enough to start working immediately.