---
name: fast-path
user-invocable: true
description: |
  T0/T1 タスク専用の最短経路スキル。spec 文書を一切要求せず、必要最小限のプロセスだけを通す。
  T0 (typo, rename, ≤10行) は直接編集、T1 (単一関数追加, バグ修正) は TDD + verification のみ。
  Use for trivial and small tasks: typo fixes, renames, single-function additions, bug fixes.
  Trigger on "tier:T0", "tier:T1", "ちょっとした修正", "typo直して", "quick fix", "small change",
  "この関数を追加", "バグ修正". Do NOT trigger on T2/T3 tasks or anything requiring spec documents.
  This skill is self-contained and MUST NOT delegate to any `superpowers:*` skill.
---

# fast-path

## Independence

This skill **MUST NOT** invoke or delegate to any `superpowers:*` skill.

## Purpose

The fastest path from user request to done — skip all spec ceremony. T0 runs with zero process overhead; T1 adds TDD plus verification, and nothing else. This skill exists because most daily development is T0/T1, and forcing spec workflows onto trivial tasks kills developer joy.

## When to Trigger

- User explicitly says `tier:T0` or `tier:T1`
- Router (`spec-coexist-router`) classifies task as T0 or T1
- Task is clearly trivial: typo, rename, import cleanup, config tweak, single function, single bug fix

Do NOT trigger for T2/T3 tasks, new subsystems, or cross-cutting changes.

## T0 Procedure (trivial — zero overhead)

1. Make the edit directly.
2. Run lint/format if available.
3. Done. No TDD, no verification skill, no review.

## T1 Procedure (small — TDD + verification)

1. **Understand** — read the relevant code. No spec document needed.
2. **Test first** — invoke `spec-coexist:test-driven-implementation` for the RED-GREEN-REFACTOR cycle.
3. **Verify** — invoke `spec-coexist:verification-before-completion` (code mode).
4. **Done.** No spec creation, no design doc, no code-review-loop (unless user requests it).

## Tier Escalation

If during work the scope grows beyond T1 — for example, changes span multiple subsystems, the diff exceeds ~50 lines, or behavior changes become non-trivial — then:

1. Stop the fast-path.
2. Announce the escalation to the user, with the reason.
3. Re-route to the appropriate tier via `spec-coexist-router`.

## Flow

```mermaid
flowchart TD
    Start([Task received]) --> Tier{T0 or T1?}
    Tier -- T0 --> Edit[Direct edit + lint]
    Edit --> Done0([Done])
    Tier -- T1 --> TDD[test-driven-implementation]
    TDD --> Verify[verification-before-completion]
    Verify --> Done1([Done])
    TDD --> Esc{Scope grew?}
    Esc -- Yes --> Route[Escalate to router]
```

## References

- `../spec-coexist-router/references/task-tiers.md` — tier definitions
- `../spec-coexist-router/references/tier-examples.md` — examples for T0/T1 boundary cases

## Scripts

None. This skill invokes sub-skills directly; no additional scripts needed.