---
description: Deep thinking with sequential reasoning
argument-hint: "[topic or task-id]"
agent: oracle
---

# Think: $ARGUMENTS

## For General Problem-Solving (No Task)

**Proceed if:**

- Complex problem needs structured thinking
- Multiple approaches should be considered
- Design decisions needed
- No task structure

Use sequential thinking with:

1. Problem structuring
2. Solution exploration
3. Constraint research
4. Design options
5. Trade-off analysis
6. Decision reasoning

---

## For Task-Constrained Thinking (With Task Files)

## Phase 1: Task Validation

### Check Task Exists

Check task exists via backlog_task_view({ id: "$ARGUMENTS" }), then verify files in `@backlog/tasks/$ARGUMENTS/`: prd.md + spec.md

**If missing:** Create with `/task-with-spec "$ARGUMENTS"` first.

### Load Thinking Boundaries

From PRD:

- Goal
- Scope

From Spec:

- Constraints

## Phase 2: Task-Context Problem Structuring

### Structure Only Task-Related Problem

**Task Problem:** [From PRD goal section]
**Task Boundaries:** [From PRD scope section]
**Task Constraints:** [From spec constraints section]

### Sequential Thinking (Task-Focused):

```
Use sequential-thinking for task $ARGUMENTS analysis

ANTI-HALLUCINATION THINKING REQUIREMENTS:
1. Read $TASK_DIR/prd.md and spec.md FIRST
2. Structure thinking only around task goal
3. Explore solutions within task scope only
4. Apply problem-solving techniques to task constraints
5. Reject approaches outside task boundaries
6. Document thinking in review.md
7. Stay within task-defined problem space

THINKING BOUNDARIES:
- Goal: [From PRD goal]
- Scope: [From PRD scope]
- Constraints: [From spec constraints]
- Success: [From PRD success criteria]

NO EXCEPTIONS: Thinking must serve task requirements only
```

### Questions to Explore (Task-Bounded):

1. **Task Problem**: What's the real problem within task goal?
2. **Task Assumptions**: What assumptions does task $ARGUMENTS make?
3. **Task Boundaries**: What would task $ARGUMENTS look like from zero?
4. **Task Elegance**: What's most elegant solution within task constraints?

## Phase 3: Task-Problem Solving

### Apply Techniques (Task-Context)

| Problem Type                  | Technique          | Task Application                       |
| ----------------------------- | ------------------ | -------------------------------------- |
| Complexity within task        | Simplification     | Remove non-essential task features     |
| Innovation within constraints | Collision thinking | Combine task elements in new ways      |
| Patterns within scope         | Meta-recognition   | Find recurring patterns in task domain |
| Assumptions in task           | Inversion          | What if opposite of task assumption?   |

### Technique Selection (Task-Bounded):

- Choose technique that serves task goal
- Apply within task scope boundaries
- Respect all task constraints
- Work toward task success criteria

## Phase 4: Task-Solution Design

### Design Within Task Constraints

**Solution Space**: [Limited by task scope]
**Design Rules**: [From task spec constraints]
**Success Metrics**: [From task PRD criteria]

### Solution Options (Task-Only):

```
Option 1: [Task-compliant approach]
- Core Idea: [Within task constraints]
- Pros: [Serves task goal]
- Cons: [Within task limitations]
- Complexity: [Appropriate for task]

Option 2: [Alternative task approach]
- Core Idea: [Different take on task goal]
- Pros: [Still within task scope]
- Cons: [Task constraint challenges]
- Complexity: [Fits task requirements]

Option 3: [Contrarian within task]
- Core Idea: [Opposite of task assumption]
- Pros: [Unexpected task benefits]
- Cons: [Task boundary conflicts]
- Complexity: [Task-appropriate]
```

## Phase 5: Task-Craftsmanship Test

### Validate Against Task Requirements

✓ **Simpler possible?** [Within task constraints]
✓ **Necessary for task?** [For task success]
✓ **Inevitable for task?** [Serves task goal]
✓ **Task-explainable?** [One sentence about task]
✓ **Task-survivable?** [5 years for task context]

### Task Elegance Check:

> Solution should feel inevitable for task $ARGUMENTS
> If defending complexity for task, haven't thought deep enough

## Phase 6: Task Implementation Blueprint

### Task-Focused Plan

1. **Step**: [Clear task progression]
2. **Next**: [Natural task step]
3. **Final**: [Task completion]

### Task Edge Cases:

- [From task spec edge cases]
- [Task-specific error handling]
- [Task constraint compliance]

### Task Verification:

- [ ] Meets task PRD success criteria
- [ ] Follows task spec constraints
- [ ] Stays within task scope
- [ ] Handles task edge cases

## Phase 7: Task Documentation

### Update Task Review

Document in review.md:

- Task analysis (problem, constraints, scope)
- Solution process within task boundaries
- Decision rationale
- Task compliance verification

---

**ANTI-HALLUCINATION: Task thinking validates against constraints; general thinking is unrestricted**
