Reads a site feature specification file and converts it into a structured, actionable development task list saved to the project memory bank. Use when you need to break down requirements into developer tasks, plan project work from a PRD or spec, convert feature specifications into tickets with acceptance criteria, or create a task breakdown from site-setup documentation. Produces per-task acceptance criteria, file references, and technical stack notes drawn exclusively from the specification — no scope creep or unspecified features added.
93%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Passed
No findings from the security scan
ai/memory-bank/site-setup.md (the canonical spec file)name, email, message fields; mail action sends to info@example.com; show success message on submit"ai/memory-bank/tasks/[project-slug]-tasklist.md# [Project Name] Development Tasks
## Specification Summary
**Original Requirements**: [Quote key requirements verbatim from spec]
**Technical Stack**: [Laravel, Livewire, FluxUI, Alpine.js, etc. — from spec]
**Target Timeline**: [From specification]
## Development Tasks
### [ ] Task 1: Basic Page Structure
**Description**: Create main page layout with header, content sections, footer
**Acceptance Criteria**:
- Page loads without errors
- All sections from spec are present
- Basic responsive layout works
**Files to Create/Edit**:
- `resources/views/home.blade.php`
- Basic CSS structure
**Spec Reference**: [Section name / line from site-setup.md]
### [ ] Task 2: Navigation Implementation
**Description**: Implement working navigation with smooth scroll
**Acceptance Criteria**:
- Navigation links scroll to correct sections
- Mobile menu opens/closes
- Active states show current section
**Components**: `flux:navbar`, Alpine.js interactions
**Spec Reference**: [Section name / line from site-setup.md]
[Continue for all major features…]
## Quality Requirements
- [ ] All FluxUI components use supported props only
- [ ] No background processes — NEVER append `&` to any command
- [ ] No server startup commands — assume development server is already running
- [ ] Mobile responsive design required
- [ ] Form functionality must work (if forms are in spec)
- [ ] Images from approved sources only: Unsplash, `https://picsum.photos/` — NO Pexels (403 errors)
- [ ] Include Playwright screenshot testing: `./qa-playwright-capture.sh http://localhost:8000 public/qa-screenshots`
## Assumptions & Flagged Gaps
- [List any tasks added without a direct spec reference, or requirements that are ambiguous]
## Technical Notes
**Development Stack**: [Exact requirements from spec]
**Special Instructions**: [Client-specific requests from spec]
**Timeline Expectations**: [Realistic based on scope]Full methodology and examples: ai/agents/pm.md
OpenRoster-ai/awesome-agents
010799b
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.