← ClaudeAtlas

claude-docslisted

Updates `.claude/` planning docs to reflect decisions made during the session. Use when design or requirements changed mid-cycle, after discussing a pivot, or before shipping when the session diverged from the original plan. Do NOT use for task promotion or archiving. Edit `.claude/TASKS.md` directly for that.
erclx/toolkit · ★ 1 · AI & Automation · score 74
Install: claude install-skill erclx/toolkit
# Claude docs ## Guards - If no `.claude/` directory exists, stop: `❌ No .claude/ directory found. Run aitk claude init to set up the workflow.` - If no decisions were made in this session that differ from the original plan, stop: `✅ No doc updates needed. Session matched the original plan.` ## Step 1: read current docs Read these in parallel from the current worktree root (`pwd`), not the main worktree root. These are tracked files and edits must commit with the branch. Skip any that do not exist: - `.claude/TASKS.md` - `.claude/REQUIREMENTS.md` - `.claude/ARCHITECTURE.md` - `.claude/DESIGN.md` - `.claude/wireframes/index.md` and every `.claude/wireframes/<surface>.md` ## Step 2: identify what changed Review the session for decisions that diverged from the original plan: - Requirements added, removed, or changed scope - Architecture or technical decisions made or revised - Design or UX decisions that differ from DESIGN.md or any `.claude/wireframes/<surface>.md` - Tasks completed, blocked, or newly identified ## Step 3: update For each doc with relevant changes, apply updates following these rules: **TASKS.md** - Mark completed tasks `[x]` in place within "Up next". Do not move them to Done. - Add newly identified tasks to "Up next". - Do not reorder, reformat, or touch tasks that did not change. **REQUIREMENTS.md, ARCHITECTURE.md, DESIGN.md, `.claude/wireframes/<surface>.md`** - Update only the sections affected by session decisions. - Do not rewrite sections