task-list-creator

Create or update the task list artifact from gathered requirements

12 stars

Best use case

task-list-creator is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

Create or update the task list artifact from gathered requirements

Teams using task-list-creator should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

  • You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

  • You only need a quick one-off answer and do not need a reusable workflow.
  • You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/task-list-creator/SKILL.md --create-dirs "https://raw.githubusercontent.com/AlteredCraft/claude-code-plugins/main/plugins/artifact-workflow/skills/task-list-creator/SKILL.md"

Manual Installation

  1. Download SKILL.md from GitHub
  2. Place it in .claude/skills/task-list-creator/SKILL.md inside your project
  3. Restart your AI agent — it will auto-discover the skill

How task-list-creator Compares

Feature / Agenttask-list-creatorStandard Approach
Platform SupportNot specifiedLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/A

Frequently Asked Questions

What does this skill do?

Create or update the task list artifact from gathered requirements

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

SKILL.md Source

You are creating the **Task List artifact** (`todo.md`) for an artifact-driven development workflow.

## Input Context

You have access to the interrogation context from the conversation—requirements, scope, constraints, and success criteria gathered from the user.

## Your Task

Create `.artifacts/bld-<project-slug>/todo.md` (create the directory if it doesn't exist).

## Task Structure

Organize tasks into three phases with hierarchical nesting:

### Planning Phase
Research, design decisions, and technical approach tasks that happen before coding.

### Implementation Phase
The actual build work. Group related tasks under parent items with subtasks:
- Parent task (e.g., "Implement backend API aggregation service")
  - Subtask (e.g., "Integrate multiple weather data sources")
  - Subtask (e.g., "Implement data normalization layer")

### Verification Phase
Testing, validation, and documentation tasks.

## Task Decomposition Principles

1. **Phase-first thinking** — What research/design must happen before building? What verification happens after?

2. **Hierarchical grouping** — Group related implementation work under parent tasks. Subtasks should be completable independently but contribute to the parent goal.

3. **Atomic subtasks** — Each subtask is a single, verifiable unit. Parent tasks complete when all subtasks complete.

4. **Include the unsexy work** — Error handling, edge cases, fallbacks deserve explicit tasks.

5. **Verification is a phase** — Not an afterthought. Testing, edge case validation, and documentation are first-class tasks.

## For Existing Codebases

If working within an existing codebase:
- Add planning tasks for exploring/understanding current patterns
- Note integration points in implementation subtasks
- Add verification tasks for regression testing

## Artifact Structure

```markdown
---
status: in-progress
created: <timestamp> (ex: 2025-12-09 08:47:19 -0800)
updated: <timestamp> (ex: 2025-12-09 08:49:30 -0800)
project: <project-slug>
description: "<one-line summary>"
---

# <Project Name>

## Planning Phase
- [x] Research X and their capabilities
- [x] Design system architecture and data flow
- [ ] Create implementation plan document
- [ ] Get user approval on technical approach

## Implementation Phase
- [ ] Set up project structure and dependencies
- [ ] Implement backend service
  - [ ] Subtask one
  - [ ] Subtask two
  - [ ] Subtask three
- [ ] Build frontend interface
  - [ ] Subtask one
  - [ ] Subtask two
- [ ] Add error handling and fallbacks

## Verification Phase
- [ ] Test with multiple scenarios
- [ ] Verify core functionality
- [ ] Test edge cases and error scenarios
- [ ] Create walkthrough documentation
```

## Updating the Task List

As work progresses, update checkboxes:
- `- [ ]` → pending
- `- [~]` → in-progress (optional, for visibility)
- `- [x]` → complete

**IMPORTANT**: Every time you modify `todo.md`, update the `updated:` field in the frontmatter with the current timestamp.

## After Creation

Present the artifact to the user for review before proceeding.

**When presenting**, always:
1. Show the file path at the top: `📄 .artifacts/bld-<project-slug>/todo.md`
2. Display the full markdown content as it appears in the file
3. Use checkbox format showing current state:

```
[x] Completed task
[ ] Pending task
  [ ] Nested subtask
  [x] Completed subtask
```

This format makes progress immediately visible to the user.

Related Skills

walkthrough-creator

12
from AlteredCraft/claude-code-plugins

Create and maintain the walkthrough artifact during implementation

implementation-plan-creator

12
from AlteredCraft/claude-code-plugins

Create the implementation plan artifact from an approved task list

feature-spec-creator

12
from AlteredCraft/claude-code-plugins

Generates a feature spec for an existing codebase via an interview workflow. Use when the user wants to write, draft, or scope a feature spec — phrases like "write a feature spec", "spec out this feature", "draft a spec for X", "I want to add X to this codebase", "let's plan a new feature", or "scope out this feature". Do NOT use for bug fixes, pure refactors with no behavior change, or greenfield projects with no existing code.

obsidian-cli

12
from AlteredCraft/claude-code-plugins

Use the Obsidian CLI to manage knowledge in an Obsidian vault — daily notes, search, tasks, tags, link graph analysis, properties, templates, and file operations. This skill should be used when the user asks to interact with their Obsidian vault, manage daily notes, search notes, manage tasks, explore tags or backlinks, set properties, use templates, or perform vault maintenance.

qr-code

12
from AlteredCraft/claude-code-plugins

Generate QR codes from URLs, text, or other data and save them as SVG, PNG, EPS, or PDF files. This skill should be used when the user asks to create, generate, or make a QR code for any content such as website URLs, text strings, WiFi credentials, contact info, or other data. Triggers include mentions of 'QR code', 'QR', 'barcode for a link', or requests to make a scannable code. Supports customization of colors, size, error correction level, and output format.

powerpoint

12
from AlteredCraft/claude-code-plugins

Create professional PowerPoint presentations. Use when asked to "create a PowerPoint", "make a presentation", "build slides", or generate pptx files.

pdf-ocr

12
from AlteredCraft/claude-code-plugins

Parse PDF files to markdown using GLM-OCR via Ollama locally. Converts each page to an image, runs OCR, and outputs clean markdown. Use when the user wants to extract text from a PDF.

ralph-method

12
from AlteredCraft/claude-code-plugins

Set up a Ralph Wiggum task - runs Phase 1 (requirements interview) and Phase 2 (implementation planning), then stops with instructions to run the building loop. Creates namespaced specs in specs/[task-name]/.

journal

12
from AlteredCraft/claude-code-plugins

An agent to journal developer activity over a specified time period.

adr-manager

12
from AlteredCraft/claude-code-plugins

Add Architecture Decision Record (ADR) entries to an ADR file. This skill should be used when recording significant architectural decisions during development. It handles formatting and appending entries using Michael Nygard's ADR template.

essay-draft-from-research

12
from AlteredCraft/claude-code-plugins

Produces a long-form essay draft grounded in a user-supplied directory of research documents via an interview workflow. Use whenever the user wants to "draft an essay from my research", "write an essay from these notes", "turn this research directory into an essay", "I've been collecting notes on X, help me draft an essay", or "draft a long-form piece using these sources". Do NOT use for: one-shot summarization of a single document, short notes or tweets under ~600 words, pure research-findings synthesis with no drafting, or essay drafting when there is no research corpus to ground in.

create-skill

12
from AlteredCraft/claude-code-plugins

Creates a new Claude Code skill that follows the Anchored Interview pattern — ground in a CORPUS, run an interview anchored by that grounding, then produce a single ARTIFACT. Use whenever the user wants to scaffold, generate, or design an interview-style skill — phrases like "make me an anchored interview skill", "create a skill that interviews me about X and produces Y", "scaffold a skill that reads my <corpus> and writes a <artifact>", "I want a skill for spec/draft/plan/findings creation via interview", or any request to build a skill that has the ground-then-ask-then-act shape. Do NOT use for: running an anchored interview on a specific task (this skill *creates* such skills, it doesn't perform them — for that, use or create the appropriate task-specific skill); editing an existing SKILL.md; one-shot transformations with no judgment calls; or skills where there is no corpus to ground in.