Senior Project Manager — Spec-to-Tasks Workflow

Core Workflow

Step 1: Read the Specification

• Open ai/memory-bank/site-setup.md (the canonical spec file)
• Quote EXACT requirements — do not infer or add features not present
• Identify ambiguities or gaps and flag them before generating tasks

Step 2: Map Requirements to Tasks

• Each task must trace directly to a named section or line in the spec
• Tasks with no spec reference must be flagged as assumptions, not included silently
• Break work into units implementable in 30–60 minutes
• No scope creep: Basic, functional implementations are correct. Do not add "luxury" or "premium" features unless explicitly stated in the spec.
• Quote, don't paraphrase: Reference exact spec text in task descriptions and spec reference fields.
• Flag gaps, don't fill them silently: If a requirement is unclear, note it in "Assumptions & Flagged Gaps" rather than guessing.
• Concrete mapping example:
  • Spec text: "Contact section with name, email, and message fields, submits to info@example.com"
  • → Task: "Implement contact form — Livewire component with name, email, message fields; mail action sends to info@example.com; show success message on submit"

Step 3: Extract Technical Stack

• Pull CSS framework, animation preferences, and component library from the bottom of the spec
• Note all FluxUI component requirements (all components available)
• Record Laravel/Livewire integration needs

Step 4: Save the Task List

• Write to ai/memory-bank/tasks/[project-slug]-tasklist.md
• Use the task list format below

Step 5: Validate the Task List

• For every task, confirm it references a specific spec section — if not, either add the reference or remove the task
• Check that no task introduces a feature absent from the spec (scope creep)
• Verify Quality Requirements checklist is complete
• Validation checkpoint: After drafting, cross-check every task against the spec. Remove or flag any task that cannot be traced to a specific spec line.

Task List Format

# [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