Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From persistent-planning
Add a task under an existing phase in lg-mode persistent-planning. Creates .planning/<phase>/<task-slug>/{task.md, notes.md, atoms/}. Requires --parent <phase-slug>. Lg mode only.
npx claudepluginhub theglitchking/persistent-planningHow this command is triggered — by the user, by Claude, or both
Slash command
/persistent-planning:start-taskThe summary Claude sees in its command listing — used to decide when to auto-load this command
# /start-task Add a task under an existing phase. **Lg mode only** — refuses to run in sm mode. --- ## Usage ## Examples --- ## What To Do When the user runs `/start-task "<name>" --parent <phase-slug>`: 1. Run the init script: If the script isn't found at that path, try: 2. After completion, remind the user: - Edit `.planning/<phase>/<task-slug>/task.md` to define the task goal - Add atoms with `/start-atom "<name>" --parent <task-slug>` (or inline checkboxes for simple atoms) - Update task frontmatter: `depends_on: [<other-task-slug>]` for sequential dependencies,...
/start-taskStarts a new development task by assessing complexity, running pre-task checks, and guiding the user through an appropriate workflow.
Share bugs, ideas, or general feedback.
Add a task under an existing phase. Lg mode only — refuses to run in sm mode.
/start-task "Task name" --parent <phase-slug>
/start-task "HEWTD schema extension" --parent foundation
/start-task "Multi-corpus refactor" --parent semantic-memory-core
/start-task "Drift detection algorithm" --parent ecosystem-extensions
When the user runs /start-task "<name>" --parent <phase-slug>:
SCRIPT_DIR="$(dirname "$(readlink -f "$0")")/../scripts"
bash "${SCRIPT_DIR}/init-task.sh" "<name>" --parent "<phase-slug>"
If the script isn't found at that path, try:
bash scripts/init-task.sh "<name>" --parent "<phase-slug>"
bash ~/.claude/skills/persistent-planning/scripts/init-task.sh "<name>" --parent "<phase-slug>"
.planning/<phase>/<task-slug>/task.md to define the task goal/start-atom "<name>" --parent <task-slug> (or inline checkboxes for simple atoms)depends_on: [<other-task-slug>] for sequential dependencies, or parallelizable: true for tasks with no inter-dependencies.planning/<phase-slug>/
└── <task-slug>/
├── task.md # HEWTD-frontmattered task artifact (parent: <phase-slug>)
├── notes.md # Cross-cutting notes scoped to this task
└── atoms/ # Empty dir for future atoms (subagent hand-off units)
The task.md template includes two key scheduling fields:
depends_on: [] — array of other task slugs (within the same phase) this task depends on. The planning MCP's next_task() verb respects this graph.parallelizable: false — set to true for tasks that can be picked up in any order by subagent teams. Default false (conservative).This command refuses to run if the project is in sm mode. To switch:
/start-planning "<phase name>" --mode lg
That writes .planning/.meta/workspace.json with mode: "lg" and creates the first phase.
/start-planning — initialize the planning structure (phase in lg, task in sm)/start-atom — add an atom under a taskdocs/lg-mode.md — full lg-mode layer modeldocs/atom-granularity.md — when to spawn an atom file vs. add an inline checkbox