agentic-coding: Skill for Claude Code

Agent Planning — Self-Maintenance

Write lightweight implementation plans for this toolkit repo. There is no application code — the maintenance surface is markdown templates and bash scripts.

Announce at start: "I'm using the agent-planning skill to create the implementation plan."

Save plans to: plans/YYYY-MM-DD-<feature-name>/plan.md, next to the spec.

Scope Check

If the spec covers multiple independent concerns, suggest splitting into separate plans.

File Mapping

Before defining tasks, map out which files will be created or modified. For each file:

• What it is responsible for
• Whether a stacks/* overlay also needs updating (core+stacks dual-maintenance)
• Whether README.md, this repo's skills-lock.json, core/skills-lock.json, or the dot-mapping table need updates for their distinct scopes

Task Granularity

Each task is one focused commit. Steps within a task are small concrete actions:

• "Write the file" — step
• "Verify syntax" — step
• "Commit" — step

Verification should match the changed files: shellcheck and bash -n for bash scripts, smoke runs for script behavior changes, codespell for prose-heavy changes, and consistency checks for README, lockfiles, symlinks, and dot-mapping.

Spellcheck Planning

When a task creates or modifies markdown templates, agent files, skill files, README content, or user-facing script text, include a codespell verification step for the changed files. Keep it scoped to the files touched by the task unless the plan intentionally adds or updates repo-wide spelling policy.

Plan Document Header

# [Feature Name] Implementation Plan

> **For implementation agents:** Execute this plan task-by-task. Steps use checkbox (`- [ ]`) syntax for tracking.

**Goal:** [One sentence]

**Configuration shape:** [2-3 sentences]

**Configuration surface:** [Key files, tools, and validation commands]

Task Structure

### Task N: [Component Name]

**Files:**
- Create: `exact/path/to/file`
- Modify: `exact/path/to/existing`

- [ ] **Step 1: [Action]**

[Content — exact paths, complete file content or commands]

- [ ] **Step 2: Verify**

Run: `shellcheck scripts/foo.sh`
Run: `codespell exact/path/to/file.md`
Expected: no errors

- [ ] **Step 3: Commit**

```bash
git add path/to/file
git commit -m "chore: description"