Prompt file imported from Davechpn/streamlined-property-portal (.github/prompts/speckit.tasks.prompt.md). Copyright stays with the author.

Speckit Tasks Command

Name: speckit.tasks
Author: Davechpn

Purpose

The /speckit.tasks command transforms the implementation plan into granular, actionable tasks that can be assigned, tracked, and completed independently. Each task represents 2-4 hours of focused work and includes clear acceptance criteria.

Prerequisites

Before running /speckit.tasks:

✅ Implementation plan exists at .specify/specs/[###-feature-name]/plan.md
✅ All design documents are complete (research, data-model, component-hierarchy, contracts, quickstart)
✅ Plan phases are clearly defined with deliverables
✅ Feature branch is checked out

Workflow

Step 1: Read Implementation Plan

Read the plan.md file to understand:

Implementation phases and timeline
Deliverables per phase
Files to create
Testing requirements
Dependencies between tasks

Step 2: Create Task Breakdown

For each phase in the plan, break down deliverables into atomic tasks.

Task Granularity Rules:

Each task should take 2-4 hours (half a work day max)
Tasks should be independently testable
Tasks should have clear start/end points
Dependencies should be minimal and explicit

Task Structure:

### Task [PHASE]-[NUMBER]: [Clear Action Verb] [Component/Feature]

**Phase**: [Phase Number and Name]  
**Estimated Time**: [2-4 hours]  
**Dependencies**: [Task IDs this depends on, or "None"]  
**Priority**: [P0 (blocking) / P1 (high) / P2 (medium) / P3 (low)]

**Description**:
[1-2 sentences describing what needs to be done]

**Files to Create/Modify**:
- `path/to/file1.tsx` - [What this file does]
- `path/to/file2.ts` - [What this file does]

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

**Testing**:
- [How to verify this task is complete]

**Notes**:
- [Any important context, gotchas, or references]

Step 3: Organize by Phase

Group tasks by implementation phase:

Phase 1: Foundation & Landing
Phase 2: Authentication
Phase 3: Dashboard & Organizations
Phase 4: Team Management
Phase 5: Platform Administration

Step 4: Identify Dependencies

Mark task dependencies clearly:

Setup tasks (install dependencies, configure tools)
Foundation tasks (hooks, API client, types)
Feature tasks (components, pages)
Integration tasks (connect components to data)
Testing tasks (unit tests, E2E tests)

Step 5: Create Task Document

Create .specify/specs/[###-feature-name]/tasks.md with:

Task summary (total count, estimated time)
Tasks organized by phase
Dependency graph (visual representation)
Progress tracking checkboxes

Task Breakdown Template

# Task Breakdown: [Feature Name]

**Branch**: `###-feature-name`  
**Created**: [DATE]  
**Plan**: [link to plan.md]

## Summary

**Total Tasks**: [COUNT]  
**Estimated Time**: [TOTAL HOURS] hours (~[WEEKS] weeks)  
**Current Phase**: Not Started

**Progress**: 0 / [COUNT] tasks complete (0%)

---

## Phase 1: [Phase Name] ([X] tasks, [Y] hours)

### Task 1-1: [Action] [Component]
[Full task structure as shown above]

### Task 1-2: [Action] [Component]
[Full task structure as shown above]

---

## Phase 2: [Phase Name] ([X] tasks, [Y] hours)

[Continue with all tasks...]

---

## Task Dependency Graph

```mermaid
graph TD
    1-1[Task 1-1: Setup] --> 1-2[Task 1-2: Config]
    1-2 --> 2-1[Task 2-1: Component]
    1-2 --> 2-2[Task 2-2: Hook]
    2-1 --> 2-3[Task 2-3: Integration]
    2-2 --> 2-3

Progress Tracking

Phase 1: Foundation & Landing

Task 1-1
Task 1-2
Task 1-3 [etc.]

Phase 2: Authentication

Task 2-1
Task 2-2 [etc.]

Task Prioritization

P0 - Blocking (Must Do First):

Task 1-1, 1-2, 1-3 (setup and configuration)

P1 - High Priority (Core Features):

Task 2-1, 2-2, 3-1, 3-2 (authentication, dashboard)

P2 - Medium Priority (Important Features):

Task 4-1, 4-2 (team management, RBAC)

P3 - Low Priority (Admin Features):

Task 5-1, 5-2 (platform admin)

Quick Reference

Current Sprint: Phase [X]
Next Task: Task [X-Y]
Blocked Tasks: [List any blocked tasks]

Notes

All tasks assume constitution compliance (Next.js, TypeScript, shadcn, TanStack Query)
Each task should be committed separately with descriptive commit message
Run tests after each task completion
Update this document as tasks are completed


## Task Breakdown Guidelines

### Foundation Tasks (Phase 1)
Break down into:
1. **Dependency Installation** (1 task)
   - Install all npm packages
   - Install shadcn components for phase
   
2. **Configuration Setup** (1-2 tasks)
   - Configure Sentry
   - Set up TanStack Query provider
   - Create API client

3. **Type Definitions** (1 task)
   - Copy and organize type definitions

4. **Landing Page** (3-4 tasks)
   - Create navigation component
   - Create hero section
   - Create features section
   - Create footer

### Authentication Tasks (Phase 2)
Break down into:
1. **Auth Infrastructure** (2-3 tasks)
   - Create auth hooks
   - Create auth API client
   - Set up middleware

2. **Auth UI** (4-6 tasks)
   - Create auth layout
   - Create sign-in form
   - Create sign-up form
   - Create password reset
   - Create OTP components

3. **Auth Integration** (1-2 tasks)
   - Connect forms to API
   - Test auth flows

### Dashboard Tasks (Phase 3)
Break down into:
1. **Dashboard Infrastructure** (2-3 tasks)
   - Install sidebar-07
   - Create organization hooks
   - Create dashboard layout

2. **Dashboard Components** (3-4 tasks)
   - Create workspace switcher
   - Create user menu
   - Create empty state
   - Create org creation dialog

3. **Dashboard Integration** (1-2 tasks)
   - Connect components to data
   - Test workspace switching

### Team Management Tasks (Phase 4)
Break down into:
1. **Team Infrastructure** (2-3 tasks)
   - Create member/invitation hooks
   - Create permissions hook
   - Set up RBAC helpers

2. **Team Components** (4-6 tasks)
   - Create member table
   - Create invitation dialog
   - Create pending invitations view
   - Create invitation acceptance page
   - Create role selector
   - Create remove member dialog

3. **RBAC Implementation** (2-3 tasks)
   - Implement permission-based rendering
   - Add role restrictions
   - Test RBAC enforcement

### Admin Tasks (Phase 5)
Break down into:
1. **Admin Infrastructure** (2-3 tasks)
   - Create admin hooks
   - Create admin layout
   - Set up admin routes

2. **Admin Components** (5-8 tasks)
   - Create admin dashboard
   - Create org list/detail
   - Create activity table
   - Create compensation report
   - Create audit trail
   - Create role manager

3. **Admin Integration** (1-2 tasks)
   - Connect admin features
   - Test admin permissions

## Best Practices

### Task Naming
- Use action verbs: Create, Implement, Add, Set up, Configure
- Be specific: "Create sign-in form" not "Build auth"
- Include component/feature name

### Task Sizing
- If task > 4 hours, split it into smaller tasks
- If task < 1 hour, consider combining with related task
- Each task should produce tangible output (file, feature, test)

### Dependencies
- Minimize cross-phase dependencies
- Setup tasks should be completed first
- Infrastructure before UI
- Components before integration

### Acceptance Criteria
- Make criteria testable and objective
- Include both functionality and quality checks
- Reference spec requirements when applicable

### Testing
- Each task should include how to test it
- Manual testing steps for UI tasks
- Unit test requirements for logic
- Integration test checkpoints

## Output Format

When user invokes `/speckit.tasks`:

Creating Task Breakdown: [Feature Name]

I'll break down the implementation plan into granular, actionable tasks.

Analysis

Reading implementation plan...

5 phases identified
total deliverables
Estimated [Y] development days

Breaking down Phase 1: Foundation & Landing...

[N] tasks created (Setup, Landing Page, Configuration)

Breaking down Phase 2: Authentication...

[N] tasks created (Auth Infrastructure, Auth UI, Integration)

Breaking down Phase 3: Dashboard & Organizations...

[N] tasks created (Dashboard Infrastructure, Components, Integration)

Breaking down Phase 4: Team Management...

[N] tasks created (Team Infrastructure, Components, RBAC)

Breaking down Phase 5: Platform Administration...

[N] tasks created (Admin Infrastructure, Components, Integration)

Task Summary

Total Tasks: [COUNT] Estimated Hours: [HOURS] hours Estimated Timeline: [WEEKS] weeks

Tasks by Phase:

Phase 1: [N] tasks ([H] hours)
Phase 2: [N] tasks ([H] hours)
Phase 3: [N] tasks ([H] hours)
Phase 4: [N] tasks ([H] hours)
Phase 5: [N] tasks ([H] hours)

Task Priorities:

P0 (Blocking): [N] tasks
P1 (High): [N] tasks
P2 (Medium): [N] tasks
P3 (Low): [N] tasks

Created: tasks.md

Next Steps

Review Tasks: Check tasks.md for completeness
Adjust Estimates: Refine time estimates if needed
Assign Tasks: Distribute tasks to team members
Start Implementation: Begin with Phase 1, Task 1-1
Track Progress: Update checkboxes as tasks complete

Ready to begin implementation? Run /speckit.implement to start coding!


## Integration with Other Commands

- **After `/speckit.plan`**: Creates granular tasks from plan phases
- **Before `/speckit.implement`**: Provides clear task list for implementation
- **Before `/speckit.taskstoissues`**: Can convert tasks to GitHub issues
- **During Implementation**: Reference for what to build next

## Notes

- Tasks should align with plan phases and deliverables
- Each task maps to quickstart.md steps where applicable
- Constitution compliance is assumed in all tasks
- Task estimates help with sprint planning
- Progress tracking helps measure velocity
- Tasks can be converted to GitHub issues for team collaboration

---

**Ready to break down your implementation plan into actionable tasks? Invoke `/speckit.tasks` with your feature branch checked out!**

# Speckit Tasks Command ## Purpose The `/speckit.tasks` command transforms the implementation plan into granular, actionable tasks that can be assigned, tracked, and completed independently. Each task represents 2-4 hours of focused work and includes clear acceptance criteria. ## Prerequisites Before running `/speckit.tasks`: - ✅ Implementation plan exists at `.specify/specs/[###-feature-name]/plan.md` - ✅ All design documents are complete (research, data-model, component-hierarchy, contracts, quickstart) - ✅ Plan phases are clearly defined with deliverables - ✅ Feature branch is checked out ## Workflow ### Step 1: Read Implementation Plan Read the `plan.md` file to understand: - Implementation phases and timeline - Deliverables per phase - Files to create - Testing requirements - Dependencies between tasks ### Step 2: Create Task Breakdown For each phase in the plan, break down deliverables into atomic tasks. **Task Granularity Rules**: - Each task should take 2-4 hours (half a work day max) - Tasks should be independently testable - Tasks should have clear start/end points - Dependencies should be minimal and explicit **Task Structure**: ```markdown ### Task [PHASE]-[NUMBER]: [Clear Action Verb] [Component/Feature] **Phase**: [Phase Number and Name] **Estimated Time**: [2-4 hours] **Dependencies**: [Task IDs this depends on, or "None"] **Priority**: [P0 (blocking) / P1 (high) / P2 (medium) / P3 (low)] **Description**: [1-2 sentences describing what needs to be done] **Files to Create/Modify**: - `path/to/file1.tsx` - [What this file does] - `path/to/file2.ts` - [What this file does] **Acceptance Criteria**: - [ ] [Specific, testable criterion 1] - [ ] [Specific, testable criterion 2] - [ ] [Specific, testable criterion 3] **Testing**: - [How to verify this task is complete] **Notes**: - [Any important context, gotchas, or references] ``` ### Step 3: Organize by Phase Group tasks by implementation phase: - Phase 1: Foundation & Landing - Phase 2: Authentication - Phase 3: Dashboard & Organizations - Phase 4: Team Management - Phase 5: Platform Administration ### Step 4: Identify Dependencies Mark task dependencies clearly: - Setup tasks (install dependencies, configure tools) - Foundation tasks (hooks, API client, types) - Feature tasks (components, pages) - Integration tasks (connect components to data) - Testing tasks (unit tests, E2E tests) ### Step 5: Create Task Document Create `.specify/specs/[###-feature-name]/tasks.md` with: - Task summary (total count, estimated time) - Tasks organized by phase - Dependency graph (visual representation) - Progress tracking checkboxes ## Task Breakdown Template ```markdown # Task Breakdown: [Feature Name] **Branch**: `###-feature-name` **Created**: [DATE] **Plan**: [link to plan.md] ## Summary **Total Tasks**: [COUNT] **Estimated Time**: [TOTAL HOURS] hours (~[WEEKS] weeks) **Current Phase**: Not Started **Progress**: 0 / [COUNT] tasks complete (0%) --- ## Phase 1: [Phase Name] ([X] tasks, [Y] hours) ### Task 1-1: [Action] [Component] [Full task structure as shown above] ### Task 1-2: [Action] [Component] [Full task structure as shown above] --- ## Phase 2: [Phase Name] ([X] tasks, [Y] hours) [Continue with all tasks...] --- ## Task Dependency Graph ```mermaid graph TD 1-1[Task 1-1: Setup] --> 1-2[Task 1-2: Config] 1-2 --> 2-1[Task 2-1: Component] 1-2 --> 2-2[Task 2-2: Hook] 2-1 --> 2-3[Task 2-3: Integration] 2-2 --> 2-3 ``` --- ## Progress Tracking ### Phase 1: Foundation & Landing - [ ] Task 1-1 - [ ] Task 1-2 - [ ] Task 1-3 [etc.] ### Phase 2: Authentication - [ ] Task 2-1 - [ ] Task 2-2 [etc.] --- ## Task Prioritization **P0 - Blocking (Must Do First)**: - Task 1-1, 1-2, 1-3 (setup and configuration) **P1 - High Priority (Core Features)**: - Task 2-1, 2-2, 3-1, 3-2 (authentication, dashboard) **P2 - Medium Priority (Important Features)**: - Task 4-1, 4-2 (team management, RBAC) **P3 - Low Priority (Admin Features)**: - Task 5-1, 5-2 (platform admin) --- ## Quick Reference **Current Sprint**: Phase [X] **Next Task**: Task [X-Y] **Blocked Tasks**: [List any blocked tasks] --- ## Notes - All tasks assume constitution compliance (Next.js, TypeScript, shadcn, TanStack Query) - Each task should be committed separately with descriptive commit message - Run tests after each task completion - Update this document as tasks are completed ``` ## Task Breakdown Guidelines ### Foundation Tasks (Phase 1) Break down into: 1. **Dependency Installation** (1 task) - Install all npm packages - Install shadcn components for phase 2. **Configuration Setup** (1-2 tasks) - Configure Sentry - Set up TanStack Query provider - Create API client 3. **Type Definitions** (1 task) - Copy and organize type definitions 4. **Landing Page** (3-4 tasks) - Create navigation component - Create hero section - Create features section - Create footer ### Authentication Tasks (Phase 2) Break down into: 1. **Auth Infrastructure** (2-3 tasks) - Create auth hooks - Create auth API client - Set up middleware 2. **Auth UI** (4-6 tasks) - Create auth layout - Create sign-in form - Create sign-up form - Create password reset - Create OTP components 3. **Auth Integration** (1-2 tasks) - Connect forms to API - Test auth flows ### Dashboard Tasks (Phase 3) Break down into: 1. **Dashboard Infrastructure** (2-3 tasks) - Install sidebar-07 - Create organization hooks - Create dashboard layout 2. **Dashboard Components** (3-4 tasks) - Create workspace switcher - Create user menu - Create empty state - Create org creation dialog 3. **Dashboard Integration** (1-2 tasks) - Connect components to data - Test workspace switching ### Team Management Tasks (Phase 4) Break down into: 1. **Team Infrastructure** (2-3 tasks) - Create member/invitation hooks - Create permissions hook - Set up RBAC helpers 2. **Team Components** (4-6 tasks) - Create member table - Create invitation dialog - Create pending invitations view - Create invitation acceptance page - Create role selector - Create remove member dialog 3. **RBAC Implementation** (2-3 tasks) - Implement permission-based rendering - Add role restrictions - Test RBAC enforcement ### Admin Tasks (Phase 5) Break down into: 1. **Admin Infrastructure** (2-3 tasks) - Create admin hooks - Create admin layout - Set up admin routes 2. **Admin Components** (5-8 tasks) - Create admin dashboard - Create org list/detail - Create activity table - Create compensation report - Create audit trail - Create role manager 3. **Admin Integration** (1-2 tasks) - Connect admin features - Test admin permissions ## Best Practices ### Task Naming - Use action verbs: Create, Implement, Add, Set up, Configure - Be specific: "Create sign-in form" not "Build auth" - Include component/feature name ### Task Sizing - If task > 4 hours, split it into smaller tasks - If task < 1 hour, consider combining with related task - Each task should produce tangible output (file, feature, test) ### Dependencies - Minimize cross-phase dependencies - Setup tasks should be completed first - Infrastructure before UI - Components before integration ### Acceptance Criteria - Make criteria testable and objective - Include both functionality and quality checks - Reference spec requirements when applicable ### Testing - Each task should include how to test it - Manual testing steps for UI tasks - Unit test requirements for logic - Integration test checkpoints ## Output Format When user invokes `/speckit.tasks`: ``` # Creating Task Breakdown: [Feature Name] I'll break down the implementation plan into granular, actionable tasks. ## Analysis Reading implementation plan... - 5 phases identified - [X] total deliverables - Estimated [Y] development days Breaking down Phase 1: Foundation & Landing... - [N] tasks created (Setup, Landing Page, Configuration) Breaking down Phase 2: Authentication... - [N] tasks created (Auth Infrastructure, Auth UI, Integration) Breaking down Phase 3: Dashboard & Organizations... - [N] tasks created (Dashboard Infrastructure, Components, Integration) Breaking down Phase 4: Team Management... - [N] tasks created (Team Infrastructure, Components, RBAC) Breaking down Phase 5: Platform Administration... - [N] tasks created (Admin Infrastructure, Components, Integration) ## Task Summary **Total Tasks**: [COUNT] **Estimated Hours**: [HOURS] hours **Estimated Timeline**: [WEEKS] weeks **Tasks by Phase**: - Phase 1: [N] tasks ([H] hours) - Phase 2: [N] tasks ([H] hours) - Phase 3: [N] tasks ([H] hours) - Phase 4: [N] tasks ([H] hours) - Phase 5: [N] tasks ([H] hours) **Task Priorities**: - P0 (Blocking): [N] tasks - P1 (High): [N] tasks - P2 (Medium): [N] tasks - P3 (Low): [N] tasks Created: tasks.md ## Next Steps 1. **Review Tasks**: Check tasks.md for completeness 2. **Adjust Estimates**: Refine time estimates if needed 3. **Assign Tasks**: Distribute tasks to team members 4. **Start Implementation**: Begin with Phase 1, Task 1-1 5. **Track Progress**: Update checkboxes as tasks complete Ready to begin implementation? Run `/speckit.implement` to start coding! ``` ## Integration with Other Commands - **After `/speckit.plan`**: Creates granular tasks from plan phases - **Before `/speckit.implement`**: Provides clear task list for implementation - **Before `/speckit.taskstoissues`**: Can convert tasks to GitHub issues - **During Implementation**: Reference for what to build next ## Notes - Tasks should align with plan phases and deliverables - Each task maps to quickstart.md steps where applicable - Constitution compliance is assumed in all tasks - Task estimates help with sprint planning - Progress tracking helps measure velocity - Tasks can be converted to GitHub issues for team collaboration --- **Ready to break down your implementation plan into actionable tasks? Invoke `/speckit.tasks` with your feature branch checked out!**

{ "prompt": "# Speckit Tasks Command\n\n## Purpose\n\nThe `/speckit.tasks` command transforms the implementation plan into granular, actionable tasks that can be assigned, tracked, and completed independently. Each task represents 2-4 hours of focused work and includes clear acceptance criteria.\n\n## Prerequisites\n\nBefore running `/speckit.tasks`:\n- ✅ Implementation plan exists at `.specify/specs/[###-feature-name]/plan.md`\n- ✅ All design documents are complete (research, data-model, component-hierarchy, contracts, quickstart)\n- ✅ Plan phases are clearly defined with deliverables\n- ✅ Feature branch is checked out\n\n## Workflow\n\n### Step 1: Read Implementation Plan\n\nRead the `plan.md` file to understand:\n- Implementation phases and timeline\n- Deliverables per phase\n- Files to create\n- Testing requirements\n- Dependencies between tasks\n\n### Step 2: Create Task Breakdown\n\nFor each phase in the plan, break down deliverables into atomic tasks.\n\n**Task Granularity Rules**:\n- Each task should take 2-4 hours (half a work day max)\n- Tasks should be independently testable\n- Tasks should have clear start/end points\n- Dependencies should be minimal and explicit\n\n**Task Structure**:\n```markdown\n### Task [PHASE]-[NUMBER]: [Clear Action Verb] [Component/Feature]\n\n**Phase**: [Phase Number and Name] \n**Estimated Time**: [2-4 hours] \n**Dependencies**: [Task IDs this depends on, or \"None\"] \n**Priority**: [P0 (blocking) / P1 (high) / P2 (medium) / P3 (low)]\n\n**Description**:\n[1-2 sentences describing what needs to be done]\n\n**Files to Create/Modify**:\n- `path/to/file1.tsx` - [What this file does]\n- `path/to/file2.ts` - [What this file does]\n\n**Acceptance Criteria**:\n- [ ] [Specific, testable criterion 1]\n- [ ] [Specific, testable criterion 2]\n- [ ] [Specific, testable criterion 3]\n\n**Testing**:\n- [How to verify this task is complete]\n\n**Notes**:\n- [Any important context, gotchas, or references]\n```\n\n### Step 3: Organize by Phase\n\nGroup tasks by implementation phase:\n- Phase 1: Foundation & Landing\n- Phase 2: Authentication\n- Phase 3: Dashboard & Organizations\n- Phase 4: Team Management\n- Phase 5: Platform Administration\n\n### Step 4: Identify Dependencies\n\nMark task dependencies clearly:\n- Setup tasks (install dependencies, configure tools)\n- Foundation tasks (hooks, API client, types)\n- Feature tasks (components, pages)\n- Integration tasks (connect components to data)\n- Testing tasks (unit tests, E2E tests)\n\n### Step 5: Create Task Document\n\nCreate `.specify/specs/[###-feature-name]/tasks.md` with:\n- Task summary (total count, estimated time)\n- Tasks organized by phase\n- Dependency graph (visual representation)\n- Progress tracking checkboxes\n\n## Task Breakdown Template\n\n```markdown\n# Task Breakdown: [Feature Name]\n\n**Branch**: `###-feature-name` \n**Created**: [DATE] \n**Plan**: [link to plan.md]\n\n## Summary\n\n**Total Tasks**: [COUNT] \n**Estimated Time**: [TOTAL HOURS] hours (~[WEEKS] weeks) \n**Current Phase**: Not Started\n\n**Progress**: 0 / [COUNT] tasks complete (0%)\n\n---\n\n## Phase 1: [Phase Name] ([X] tasks, [Y] hours)\n\n### Task 1-1: [Action] [Component]\n[Full task structure as shown above]\n\n### Task 1-2: [Action] [Component]\n[Full task structure as shown above]\n\n---\n\n## Phase 2: [Phase Name] ([X] tasks, [Y] hours)\n\n[Continue with all tasks...]\n\n---\n\n## Task Dependency Graph\n\n```mermaid\ngraph TD\n 1-1[Task 1-1: Setup] --> 1-2[Task 1-2: Config]\n 1-2 --> 2-1[Task 2-1: Component]\n 1-2 --> 2-2[Task 2-2: Hook]\n 2-1 --> 2-3[Task 2-3: Integration]\n 2-2 --> 2-3\n```\n\n---\n\n## Progress Tracking\n\n### Phase 1: Foundation & Landing\n- [ ] Task 1-1\n- [ ] Task 1-2\n- [ ] Task 1-3\n[etc.]\n\n### Phase 2: Authentication\n- [ ] Task 2-1\n- [ ] Task 2-2\n[etc.]\n\n---\n\n## Task Prioritization\n\n**P0 - Blocking (Must Do First)**:\n- Task 1-1, 1-2, 1-3 (setup and configuration)\n\n**P1 - High Priority (Core Features)**:\n- Task 2-1, 2-2, 3-1, 3-2 (authentication, dashboard)\n\n**P2 - Medium Priority (Important Features)**:\n- Task 4-1, 4-2 (team management, RBAC)\n\n**P3 - Low Priority (Admin Features)**:\n- Task 5-1, 5-2 (platform admin)\n\n---\n\n## Quick Reference\n\n**Current Sprint**: Phase [X] \n**Next Task**: Task [X-Y] \n**Blocked Tasks**: [List any blocked tasks]\n\n---\n\n## Notes\n\n- All tasks assume constitution compliance (Next.js, TypeScript, shadcn, TanStack Query)\n- Each task should be committed separately with descriptive commit message\n- Run tests after each task completion\n- Update this document as tasks are completed\n```\n\n## Task Breakdown Guidelines\n\n### Foundation Tasks (Phase 1)\nBreak down into:\n1. **Dependency Installation** (1 task)\n - Install all npm packages\n - Install shadcn components for phase\n \n2. **Configuration Setup** (1-2 tasks)\n - Configure Sentry\n - Set up TanStack Query provider\n - Create API client\n\n3. **Type Definitions** (1 task)\n - Copy and organize type definitions\n\n4. **Landing Page** (3-4 tasks)\n - Create navigation component\n - Create hero section\n - Create features section\n - Create footer\n\n### Authentication Tasks (Phase 2)\nBreak down into:\n1. **Auth Infrastructure** (2-3 tasks)\n - Create auth hooks\n - Create auth API client\n - Set up middleware\n\n2. **Auth UI** (4-6 tasks)\n - Create auth layout\n - Create sign-in form\n - Create sign-up form\n - Create password reset\n - Create OTP components\n\n3. **Auth Integration** (1-2 tasks)\n - Connect forms to API\n - Test auth flows\n\n### Dashboard Tasks (Phase 3)\nBreak down into:\n1. **Dashboard Infrastructure** (2-3 tasks)\n - Install sidebar-07\n - Create organization hooks\n - Create dashboard layout\n\n2. **Dashboard Components** (3-4 tasks)\n - Create workspace switcher\n - Create user menu\n - Create empty state\n - Create org creation dialog\n\n3. **Dashboard Integration** (1-2 tasks)\n - Connect components to data\n - Test workspace switching\n\n### Team Management Tasks (Phase 4)\nBreak down into:\n1. **Team Infrastructure** (2-3 tasks)\n - Create member/invitation hooks\n - Create permissions hook\n - Set up RBAC helpers\n\n2. **Team Components** (4-6 tasks)\n - Create member table\n - Create invitation dialog\n - Create pending invitations view\n - Create invitation acceptance page\n - Create role selector\n - Create remove member dialog\n\n3. **RBAC Implementation** (2-3 tasks)\n - Implement permission-based rendering\n - Add role restrictions\n - Test RBAC enforcement\n\n### Admin Tasks (Phase 5)\nBreak down into:\n1. **Admin Infrastructure** (2-3 tasks)\n - Create admin hooks\n - Create admin layout\n - Set up admin routes\n\n2. **Admin Components** (5-8 tasks)\n - Create admin dashboard\n - Create org list/detail\n - Create activity table\n - Create compensation report\n - Create audit trail\n - Create role manager\n\n3. **Admin Integration** (1-2 tasks)\n - Connect admin features\n - Test admin permissions\n\n## Best Practices\n\n### Task Naming\n- Use action verbs: Create, Implement, Add, Set up, Configure\n- Be specific: \"Create sign-in form\" not \"Build auth\"\n- Include component/feature name\n\n### Task Sizing\n- If task > 4 hours, split it into smaller tasks\n- If task < 1 hour, consider combining with related task\n- Each task should produce tangible output (file, feature, test)\n\n### Dependencies\n- Minimize cross-phase dependencies\n- Setup tasks should be completed first\n- Infrastructure before UI\n- Components before integration\n\n### Acceptance Criteria\n- Make criteria testable and objective\n- Include both functionality and quality checks\n- Reference spec requirements when applicable\n\n### Testing\n- Each task should include how to test it\n- Manual testing steps for UI tasks\n- Unit test requirements for logic\n- Integration test checkpoints\n\n## Output Format\n\nWhen user invokes `/speckit.tasks`:\n\n```\n# Creating Task Breakdown: [Feature Name]\n\nI'll break down the implementation plan into granular, actionable tasks.\n\n## Analysis\n\nReading implementation plan...\n- 5 phases identified\n- [X] total deliverables\n- Estimated [Y] development days\n\nBreaking down Phase 1: Foundation & Landing...\n- [N] tasks created (Setup, Landing Page, Configuration)\n\nBreaking down Phase 2: Authentication...\n- [N] tasks created (Auth Infrastructure, Auth UI, Integration)\n\nBreaking down Phase 3: Dashboard & Organizations...\n- [N] tasks created (Dashboard Infrastructure, Components, Integration)\n\nBreaking down Phase 4: Team Management...\n- [N] tasks created (Team Infrastructure, Components, RBAC)\n\nBreaking down Phase 5: Platform Administration...\n- [N] tasks created (Admin Infrastructure, Components, Integration)\n\n## Task Summary\n\n**Total Tasks**: [COUNT]\n**Estimated Hours**: [HOURS] hours\n**Estimated Timeline**: [WEEKS] weeks\n\n**Tasks by Phase**:\n- Phase 1: [N] tasks ([H] hours)\n- Phase 2: [N] tasks ([H] hours)\n- Phase 3: [N] tasks ([H] hours)\n- Phase 4: [N] tasks ([H] hours)\n- Phase 5: [N] tasks ([H] hours)\n\n**Task Priorities**:\n- P0 (Blocking): [N] tasks\n- P1 (High): [N] tasks\n- P2 (Medium): [N] tasks\n- P3 (Low): [N] tasks\n\nCreated: tasks.md\n\n## Next Steps\n\n1. **Review Tasks**: Check tasks.md for completeness\n2. **Adjust Estimates**: Refine time estimates if needed\n3. **Assign Tasks**: Distribute tasks to team members\n4. **Start Implementation**: Begin with Phase 1, Task 1-1\n5. **Track Progress**: Update checkboxes as tasks complete\n\nReady to begin implementation? Run `/speckit.implement` to start coding!\n```\n\n## Integration with Other Commands\n\n- **After `/speckit.plan`**: Creates granular tasks from plan phases\n- **Before `/speckit.implement`**: Provides clear task list for implementation\n- **Before `/speckit.taskstoissues`**: Can convert tasks to GitHub issues\n- **During Implementation**: Reference for what to build next\n\n## Notes\n\n- Tasks should align with plan phases and deliverables\n- Each task maps to quickstart.md steps where applicable\n- Constitution compliance is assumed in all tasks\n- Task estimates help with sprint planning\n- Progress tracking helps measure velocity\n- Tasks can be converted to GitHub issues for team collaboration\n\n---\n\n**Ready to break down your implementation plan into actionable tasks? Invoke `/speckit.tasks` with your feature branch checked out!**", "variables": [], "notes": "The `/speckit.tasks` command transforms the implementation plan into granular, actionable tasks that can be assigned, tracked, and completed independently. Each task represents 2-4 hours of focused work and includes clear acceptance criteria.", "metadata": { "source": { "provider": "github-prompts", "repository": "https://github.com/Davechpn/streamlined-property-portal", "path": ".github/prompts/speckit.tasks.prompt.md", "ref": "fcad4e2b96f2fbb4faf0092a8111f3fa85acc9de", "url": "https://github.com/Davechpn/streamlined-property-portal/blob/fcad4e2b96f2fbb4faf0092a8111f3fa85acc9de/.github/prompts/speckit.tasks.prompt.md", "key": "Davechpn/streamlined-property-portal/.github/prompts/speckit.tasks.prompt.md" } } }

speckit.tasks

About