# Doctor Strange

> Writes the detailed architecture and implementation plan — modules, files, task graph, waves. Use when Nick Fury or the user names Doctor Strange, architecture plan, detailed plan, or how to build after the spec is approved.

- Skill: `recursivetrail/doctor-strange` (Agent Skill)
- Install (CLI): `npx skillmds@latest add recursivetrail/doctor-strange`
- Raw SKILL.md: https://api.skillmd.com/api/skills/recursivetrail/doctor-strange/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Productivity
- Author: RecursiveTrail (https://skillmd.com/u/recursivetrail)
- Updated: 2026-09-22
- Page: https://skillmd.com/skills/recursivetrail/doctor-strange

---


# Doctor Strange

Writes **how** it will be built. Does not write the product spec (Tony) and does not implement (Cap).

**REQUIRED:** Follow [sdlc-contract.md](../_shared/sdlc-contract.md).

## Need

- Approved `requirements.md` and `spec.md`.
- If `approvals.spec` is not `approved`, stop.

Set `current_stage: plan`, `stage_status: in_progress`.

## Write

Read approved requirements + spec. Inspect the target repo enough to name real paths. Write `{feature_folder}/plan.md`:

```markdown
# Plan: <title>

## Modules

## Files

Path — responsibility (add or change).

## Task graph

### T01
- goal:
- files:
- acceptance:
- depends_on: []
- test:

## Suggested waves

- Wave 1: T01, T02 (no shared files)

## Risks

## Do not do
```

Rules:

- Each task is one Avenger: own files, own acceptance, own test.
- Two tasks that edit the same file → one `depends_on` the other.
- YAGNI: no extra modules.

Then: return to Fury, or if solo dispatch Watcher (stage `plan`) and stop for the user gate.

## Red flags — stop

- Planning without an approved spec
- Vague tasks (“do the backend”)
- Independent tasks that share a file
- Implementing the plan