← ClaudeAtlas

start-tasklisted

Front door for any request to change code. Reads the code the request touches, then decides whether it goes to the task executor, to the bugfix skill or to a spec, and asks the author when the answer is not a spec. Start a new feature or task by writing its spec before any code. Use for any request to change code that no other skill takes (not a bug the author named, which is bugfix's; not an existing spec, which is implement-spec's; not a pull request, which is pr's; not a strategy or a high or low level design, which are `strategy`, `hld` and `lld`'s; and not a typo-sized change, which needs no skill), and when asked to start, plan, spec, scope or design a task, feature or piece of work, or when a request is big enough that coding straight away would be guessing. Produces requirements.md, design.md and tasks.md in .ponderly/specs/<task-name>/, following the team's spec template, with the author approving each document before the next is written. Does not write code.
sabind/ponderly · ★ 0 · Code & Development · score 69
Install: claude install-skill sabind/ponderly
# Start a task The front door for a change: read the code the request touches, then route the request to `bugfix`, to the executor, or to a spec. On the spec route, turn the task into an approved spec before anyone writes code: requirements first, then a design that satisfies them, then an ordered task list to build it. The author approves each document before the next one starts, and owns the result. Task, as the author gave it: $ARGUMENTS ## Ground rules - **No code of your own.** Do not create or edit source files. On Spec_Route the skill ends when `tasks.md` is approved; on Bug_Route it ends at the hand-off; on Executor_Route the executor writes the code and the skill ends after reporting its Summary. - **The template is the standard.** The three files under `${CLAUDE_SKILL_DIR}/spec-template/` are self-describing: each is a valid document whose own prose explains how that kind of document works, using a Link Shortener as the worked example. Read the matching template file before writing each document. Copy its structure and its rules; do not copy its example content or its teaching notes. - **Ask, don't invent.** When something the spec needs is not in the request or the codebase, ask the author. Keep each round of questions short, and batch them. - **Approval is explicit.** "Looks good" with a "but" is a change request. Make the change and ask again. Do not move to the next document until the author says the current one is approved. - **Size to the task.** A small t