Tasks Generator

Transform PRD documents into structured, sprint-based development tasks with dependency analysis.

Repo Sync Before Edits (mandatory)

Before creating/updating/deleting files in an existing repository, sync the current branch with remote:

branch="$(git rev-parse --abbrev-ref HEAD)"
git fetch origin
git pull --rebase origin "$branch"

If the working tree is not clean, stash first, sync, then restore:

git stash push -u -m "pre-sync"
branch="$(git rev-parse --abbrev-ref HEAD)"
git fetch origin && git pull --rebase origin "$branch"
git stash pop

If origin is missing, pull is unavailable, or rebase/stash conflicts occur, stop and ask the user before continuing.

Input

Preferred: PRD file path provided in $ARGUMENTS.

Auto-pick mode (if $ARGUMENTS is empty):

1. Reuse the most recent project folder/path from this chat/session.
2. If unavailable, use env var IDEAS_ROOT when present.
3. Else check shared marker file ~/.config/ideas-root.txt.
4. Backward compatibility fallback: ~/.openclaw/ideas-root.txt.
5. If still unavailable, ask the user to provide the path or set IDEAS_ROOT.
6. Use <project>/prd.md.
7. If multiple candidates are plausible, ask user to choose.

Pre-checks

1. Resolve PRD_PATH (from $ARGUMENTS or auto-pick mode) and verify it exists
2. Check for existing tasks.md in the same directory - create backup if exists: tasks_backup_YYYY_MM_DD_HHMMSS.md
3. Look for supporting docs in same directory: tad.md, ux_design.md, brand_kit.md

Workflow

Phase 1: Extract Requirements

From PRD, extract:

• Core features and value proposition
• User stories and personas
• Functional requirements
• Non-functional requirements (performance, security)
• Technical constraints and dependencies

Phase 2: Define Development Phases

POC (Proof of Concept):

• Single most important feature proving core value
• Minimal implementation, 1-2 sprints

MVP (Minimum Viable Product):

• Essential features for first release
• Core user workflows

Full Features:

• Remaining enhancements
• Nice-to-haves and polish

Phase 3: Create Sprint Plan

Sprint	Focus	Scope
Sprint 1	POC	Core differentiating feature
Sprint 2	MVP Foundation	Auth, data models, primary workflows
Sprint 3	MVP Completion	UI/UX, integration, validation
Sprint 4+	Full Features	Enhancements, optimization, polish

Phase 4: Analyze Dependencies

1. Map Dependencies: For each task, identify "Depends On" and "Blocks"
2. Group Parallel Tasks: Assign tasks to execution waves
3. Calculate Critical Path: Longest dependency chain = minimum duration
4. Validate: Check for circular dependencies, broken references

Phase 5: Generate tasks.md

Create tasks.md in same directory as PRD. See references/tasks-template.md for full template.

Task Format

Each task must include:

### Task X.Y: [Action-oriented Title]

**Description**: What and why, referencing PRD

**Acceptance Criteria**:
- [ ] Specific, testable condition 1
- [ ] Specific, testable condition 2

**Dependencies**: None / Task X.X

**PRD Reference**: [Section]

Task Guidelines

• Title: Action-oriented (e.g., "Implement user authentication API")
• Size: 1-3 days of work; break larger features
• Criteria: Cover happy path and edge cases
• Dependencies: List prerequisites and external dependencies

Quality Checks

Before finalizing:

• All PRD requirements addressed
• Each task links to PRD
• No circular dependencies
• Clear MVP vs post-MVP distinction
• Ambiguous requirements flagged
• All tasks in dependency table
• Critical path identified

README Maintenance (ideas repo)

After writing tasks.md, if the PRD lives inside an ideas repo, update the repo README ideas table:

• Preferred: cd to the repo root and run python3 scripts/update_readme_ideas_index.py (if it exists)
• Fallback: update README.md manually (ensure Tasks status becomes ✅ for that idea)

Commit and push (mandatory)

• Commit immediately after updates.
• Push immediately to remote.
• If push is rejected: git fetch origin && git rebase origin/main && git push.

Do not ask for additional push permission once this skill is invoked.

Reporting with GitHub links (mandatory)

When reporting completion, include:

• GitHub link to tasks.md
• GitHub link to README.md when it was updated
• Commit hash

Link format (derive <owner>/<repo> from git remote get-url origin):

• https://github.com/<owner>/<repo>/blob/main/<relative-path>

Output Summary

After generating, provide:

1. File location
2. Sprint overview (count, tasks per sprint)
3. MVP scope summary
4. Dependency analysis (waves, critical path, bottlenecks)
5. Flagged ambiguous requirements
6. Next steps: Review Sprint 1 and Wave 1 tasks first