scaffold-planning
Create a lightweight `planning/` folder in the current repo with leftover-tasks.md, blockers.md, session-logs/, and handovers/.
Skill by danielrosehill
Install
Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.
npx agentmarket install skill/danielrosehill-scaffold-planning
Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.
Get the weekly diff
The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.
About
Use cases: productivity
Reviews
Write a reviewNo reviews yet. Installed it? Reviews come from verified installers only. How reviews work
Permissions
What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.
- Tools
- No tools found
- Secrets
- None asked for
- Install scripts
- None found
Network hosts it talks to 1
codeload.github.com· found in install command
Files it touches
~/.claude/skills/scaffold-planning
What's inside
- Skill name
scaffold-planning- Description
- Create a lightweight `planning/` folder in the current repo with leftover-tasks.md, blockers.md, session-logs/, and handovers/. Idempotent — leaves existing files alone. Acknowledges task-queuer's heavyweight structure if present without duplicating. Use when the user says "scaffold planning", "set up planning folder", "init planning", or when another claude-rudder skill needs the structure and finds it missing.
- License
- MIT
- Instructions
- 148 lines in SKILL.md · view on GitHub
Files (1)
- SKILL.md
SKILL.md (first lines)
# Scaffold Planning Folder
Lightweight planning structure for repos. Lives at `<repo-root>/planning/`. Designed to coexist with `task-queuer@danielrosehill`'s heavier queue if both are in use.
## What it creates
```
<repo-root>/planning/
README.md # index — what each file is for, which skills consume it
leftover-tasks.md # follow-ups deferred mid-flow (capture-leftover writes here)
blockers.md # known blockers ordered by urgency (log-blocker writes here)
session-logs/ # one file per significant session, append-only
.gitkeep
handovers/ # context-gate / handover skills write here
.gitkeep
```
## When to run
Run automatically (silently) when another claude-rudder skill needs to write to one of these files and finds it missing. Run explicitly when the user asks to set up the planning structure for a new repo.
## Idempotency
This skill **never overwrites** existing content. For each artifact:
- If file exists → skip silently
- If file missing → create with the seed content below
- If `planning/` doesn't exist at all → create the whole tree
So running it twice (or a hundred times) on the same repo is safe.
## Steps
### 1. Resolve repo root
```bash
repo_root=$(git rev-parse --show-toplevel 2>/dev/null) || repo_root="$PWD"
```
If `cwd` is not in a git repo, ask the user where to scaffold (default to cwd, but confirm).
### 2. Detect task-queuer
If `<repo-root>/planning/tasks/in-queue/` exists, task-queuer's queue is already set up here. **Don't touch its files.** Only add the lightweight artifacts (leftover-tasks.md, blockers.md, session-logs/, handovers/) alongside. The README.md should mention both systems coexist.
### 3. Create directories
```bash
mkdir -p "$repo_root/planning/session-logs" "$repo_root/planning/handovers"
touch "$repo_root/planning/session-logs/.gitkeep" "$repo_root/planning/handovers/.gitkeep"
```
### 4. Create files (only if absent)
#### `planning/leftover-tasks.md`
```markdown
# Leftover Tasks
Follow-up work surfaced mid-flow and deliberately deferred. Captured by `rudder:capture-leftover`. Tackled in fresh sessions via `session-hopper:start-leftover`.
Each entry follows this structure:
```
## YYYY-MM-DD HH:MM — <one-line summary>
- **Surfaced during:** <what we were doing>
- **Why deferred:** <reason>
- **Context:** <minimum the next session needs>
- **Estimated scope:** small | medium | large | unknown
- **Status:** open | in-progress | done
```
---
<!-- new entries appended below -->
```
#### `planning/blockers.md`
```markdown
# Blockers
Things preventing progress, ordered by urgency. Captured by `rudder:log-blocker`. Reviewed at session start, cleared individually.
Each entry follows this structure:
```
## <urgency: critical | high | normal | low> — <one-line summary>
- **Logged at:** YYYY-MM-DD HH:MM
- **Affects:** <what's blocked by this>
- **Owner:** <who needs to act, or "self" / "external">
- **Notes:** <details, attempts, next options>
- **Status:** open | resolved
```
---
<!-- new entries appended below -->
```
#### `planning/README.md`
```markdown
# Planning Folder
Lightweight planning artifacts for this repo. Read by `rudder` skills.
## Files
| File | Purpose | Writer skill | Reader skills |
|---|---|---|---|
| `leftover-tasks.md` | Follow-ups surfaced mid-flow, deferred | `capture-leftover` | `start-leftover` |
| `blockers.md` | Known blockers, ordered by urgency | `log-blocker` | (manual review) |
| `session-logs/` | Per-session summaries, append-only | (any) | `start-from-handover` may consult |
| `handovers/` | Frozen handover snapshots | `context-gate`, `handover`, `handover-with-tasks` | `start-from-handover` |
## Coexistence with task-queuer
If `task-queuer@danielrosehill` is also in use here, you'll see additional folders alongside (`tasks/in-queue/`, `tasks/holding/`, `tasks/done/`, `bug-reports/`, `project-decisions/`). Different system, different purpose:From danielrosehill/Claude-Rudder, MIT.
More from danielrosehill/Claude-Rudder
- 0.470score
context-gate
danielrosehill
One-shot context-checkpoint workflow — when the current session is getting cluttered, write a structured handover plan capturing what's done and what's…
SkillAFreshness: A★ 2Claude Code +9 - 0.470score
plugin-data-storage
danielrosehill
Canonical reference for where Claude Code plugins should persist user data.
SkillAFreshness: A★ 2Claude Code +9 - 0.470score
context-workflow-reference
danielrosehill
Reference and worked example for the CONTEXT.md / CLAUDE.md two-file workflow.
SkillAFreshness: A★ 2Claude Code +9 - 0.470score
save-plan
danielrosehill
Save a Claude Code plan (from ExitPlanMode, design discussion, or multi-step task) to persistent storage.
SkillAFreshness: A★ 2Claude Code +9 - 0.470score
install-from-github
danielrosehill
Use when the user points at a GitHub repo (an agent skill, MCP server, or "Claude plugin"-ish project) and wants to install or register it.
SkillAFreshness: A★ 2Claude Code +9 - 0.467score
setup-agent-logs
danielrosehill
First-run setup for the session log archive.
SkillAFreshness: A★ 2Claude Code +9 - 0.467score
extract-skill
danielrosehill
Synthesize a new SKILL.md from the procedure that was just followed in this session, so the next session can replay it without being briefed from scratch.
SkillAFreshness: A★ 2Claude Code +9 - 0.348score
log-blocker
danielrosehill
Append a known blocker to `<repo>/planning/blockers.md` (auto-scaffolds if missing).
SkillDFreshness: D★ 2Claude Code +9 - 0.348score
fork-new-direction
danielrosehill
Create a new repo that starts from the current repo's state but takes a new direction — copy the code, seed CLAUDE.md with the revised approach, and push.
SkillDFreshness: D★ 2Claude Code +9 - 0.348score
capture-leftover
danielrosehill
Capture a follow-up task that surfaced mid-flow but shouldn't distract from the current focus.
SkillDFreshness: D★ 2Claude Code +9 - 0.348score
mirror-to-private
danielrosehill
Create a private GitHub repo that mirrors the current public repo.
SkillDFreshness: D★ 2Claude Code +9 - 0.348score
repo-from-thread
danielrosehill
Create a new GitHub repo seeded with context from the current conversation.
SkillDFreshness: D★ 2Claude Code +9
Signals
- Stars
- 2
- Forks
- 0
- Open issues
- 0
- Last commit (this folder)
- Oct 15, 2026 (13 days ago)
From GitHub (fetched Oct 24, 2026).
Details
- License
- MIT
- Repository
- github.com/danielrosehill/Claude-Rudder
- First seen
- Oct 24, 2026
- Last checked
- Oct 24, 2026
- Source
- GitHubgithub-graphql
More from danielrosehill
- 0.470score
plugin-data-storage
danielrosehill
Canonical reference for where Claude Code plugins should persist user data.
SkillAFreshness: A★ 2Claude Code +9 - 0.470score
save-plan
danielrosehill
Save a Claude Code plan (from ExitPlanMode, design discussion, or multi-step task) to persistent storage.
SkillAFreshness: A★ 2Claude Code +9 - 0.470score
onboard
danielrosehill
First-run onboarding for the adb-ops plugin.
SkillAFreshness: A★ 2Claude Code +9 - 0.470score
context-gate
danielrosehill
One-shot context-checkpoint workflow — when the current session is getting cluttered, write a structured handover plan capturing what's done and what's…
SkillAFreshness: A★ 2Claude Code +9 - 0.470score
context-workflow-reference
danielrosehill
Reference and worked example for the CONTEXT.md / CLAUDE.md two-file workflow.
SkillAFreshness: A★ 2Claude Code +9 - 0.470score
install-from-github
danielrosehill
Use when the user points at a GitHub repo (an agent skill, MCP server, or "Claude plugin"-ish project) and wants to install or register it.
SkillAFreshness: A★ 2Claude Code +9
Cite this page
scaffold-planning skill. Agent Mart. https://agentmart.dev/skills/danielrosehill-scaffold-planning (last updated 2026-10-24)