Display detailed information for a specific task
View complete details for a specific task or subtask, including status, dependencies, acceptance criteria, and blocking information. Use this when you need to understand a task's full context, check dependency status, or review acceptance criteria before starting work.
/plugin marketplace add gaurangrshah/gsc-plugins/plugin install worklog@gsc-pluginsDisplay comprehensive details for a specific task or subtask.
.tasks/tasks.json<task-id> - Required. Task ID (e.g., 3 or 3.2 for subtask).tasks/tasks.json exists with tasks)Handle both task and subtask IDs:
3 → Top-level task with id=33.2 → Subtask 2 of task 3Read .tasks/tasks.json and find the specified task.
If not found:
Task <id> not found.
Available tasks: 1, 2, 3, 4, 5
Run /task-list to see all tasks.
For each dependency, check its current status:
for dep_id in task.dependencies:
dep_task = find_task(dep_id)
dep_status = dep_task.status
# Determine if satisfied (done) or blocking
For top-level task:
┌─────────────────────────────────────────────────────────────────┐
│ Task 3: Implement user authentication │
├─────────────────────────────────────────────────────────────────┤
│ │
│ Status: ○ pending │
│ Priority: HIGH │
│ Created: 2025-11-29 10:00 │
│ Updated: 2025-11-29 12:30 │
│ │
├─────────────────────────────────────────────────────────────────┤
│ Description │
├─────────────────────────────────────────────────────────────────┤
│ Set up JWT-based authentication flow with login, logout, and │
│ token refresh capabilities. Should integrate with existing │
│ user model from task 2. │
│ │
├─────────────────────────────────────────────────────────────────┤
│ Dependencies │
├─────────────────────────────────────────────────────────────────┤
│ ✓ Task 1: Set up project structure (done) │
│ ● Task 2: Implement database schema (in_progress) │
│ │
│ ⚠ BLOCKED: Waiting on task 2 to complete │
│ │
├─────────────────────────────────────────────────────────────────┤
│ Acceptance Criteria │
├─────────────────────────────────────────────────────────────────┤
│ ☐ Users can register with email/password │
│ ☐ Users can log in and receive JWT token │
│ ☐ Tokens expire after 24 hours │
│ ☐ Refresh token flow extends session │
│ ☐ Invalid credentials return 401 │
│ │
├─────────────────────────────────────────────────────────────────┤
│ Subtasks │
├─────────────────────────────────────────────────────────────────┤
│ (none - run /task-expand 3 to break down) │
│ │
├─────────────────────────────────────────────────────────────────┤
│ Blocking │
├─────────────────────────────────────────────────────────────────┤
│ This task blocks: │
│ → Task 4: Create API endpoints │
│ → Task 5: Add rate limiting │
│ │
└─────────────────────────────────────────────────────────────────┘
For subtask:
┌─────────────────────────────────────────────────────────────────┐
│ Subtask 3.2: Create login endpoint │
│ Parent: Task 3 - Implement user authentication │
├─────────────────────────────────────────────────────────────────┤
│ │
│ Status: ○ pending │
│ │
├─────────────────────────────────────────────────────────────────┤
│ Sibling Subtasks │
├─────────────────────────────────────────────────────────────────┤
│ ✓ 3.1 Create user registration endpoint │
│ ○ 3.2 Create login endpoint (this task) │
│ ○ 3.3 Create token refresh endpoint │
│ ○ 3.4 Create logout endpoint │
│ │
└─────────────────────────────────────────────────────────────────┘
| Status | Display | Meaning |
|---|---|---|
| Unchecked | ☐ | Not verified |
| Checked | ☑ | Verified (when task done) |
When task status is done, all criteria show as checked.
| Icon | Meaning |
|---|---|
| ✓ | Dependency satisfied (done) |
| ● | Dependency in progress |
| ○ | Dependency pending |
| ◌ | Dependency blocked |
| Error | Resolution |
|---|---|
No .tasks/tasks.json | Prompt to run /task-init |
| Task ID not found | Show available task IDs |
| Invalid ID format | Show expected format (number or number.number) |
# Show task 3 details
/task-show 3
# Show subtask 3.2 details
/task-show 3.2
# Show first task
/task-show 1