---
description: Quick task creation and implementation (simple tasks only)
agent: build
---

# Quick Build: $ARGUMENTS

**WARNING:** Only for trivial tasks (≤1 file, 0 external deps, LOW security risk). Otherwise use `/task-with-spec`

## ANTI-HALLUCINATION GATE

**REJECT if ANY of these are true:**

- Affects ≥2 files
- Adds new dependencies
- Security risk is MEDIUM or HIGH
- Requires database changes
- Involves authentication/authorization
- Scope is ambiguous

**IF REJECTED:** Stop. Create proper task with `/task-with-spec "$ARGUMENTS"` instead.

## For Simple Edits (No Task Needed)

**Proceed directly if:**

- Single file, single function/component
- Bug fix or minor enhancement
- No breaking changes
- Add clear comments explaining the change

**Example:**

```typescript
// Fix: Handle null case in error handler (issue #123)
if (!value) {
  return null;
}
```

## For Structured Tasks (Task File Needed)

**Create task with prd.md + spec.md if:**

- Multi-file changes
- New dependencies
- Complex logic requiring planning
- Database/config changes

Then follow steps below.

## Step 1: Create Minimal Task Structure (if needed)

Create three files in @backlog/tasks/[new-task-id]/:

**prd.md:**

```
# Quick Task PRD

Goal: $ARGUMENTS

Scope:
- In-Scope: Single file modification only, low complexity
- Out-of-Scope: Multi-file changes, new dependencies, security changes

Success Criteria:
- [ ] Implementation complete
- [ ] No breaking changes
- [ ] Basic testing passed
```

**spec.md:**

```
# Quick Task Spec

Architecture: Single-file modification

Constraints:
- Use existing codebase patterns only
- No new dependencies
- No security implications
- Must be reversible

Edge Cases:
- Empty/null inputs handled
- Backward compatibility maintained
```

**review.md:**

```
# Quick Task Review

What Changed: [To be filled after work]

What Skipped: [Any intentional limitations]

Inconsistencies: [Any spec deviations]

Validation: [Which success criteria are complete]
```

## Step 2: Implement Single Change

**VERIFY BEFORE MODIFYING:**

- Is the one file clearly identified?
- Does change match PRD goal exactly?
- Does it follow spec constraints?

**IMPLEMENT:** Make the change. Nothing else.

## Step 3: Fill Review.md (if task file exists)

After code change, update review.md with:

- Exact file modified and lines changed
- Function/method added or modified
- Any known limitations
- Which success criteria now complete

## Step 4: Mark Complete

Run `/complete-task [task-id]` - validates review.md complete and success criteria marked.

---

**ANTI-HALLUCINATION: Simple edits proceed with comments; complex work needs task files**
