go-fast

/go-fast

Thin entry point into a self-organizing skill chain for a fast-track task. Creates a task and passes control to idea-first. The chain then runs autonomously via Skill() calls:

go-fast → idea-first → habit-first / arch-first / audit-first → per-block cycle → ship-first

Usage:

• /go-fast {task description} — inline description
• /go-fast — asks for description

Input

A task description (inline after /go-fast or requested via prompt); optional project id from a prior /go-start invocation.

Output

A task folder {tasks_root}/log/{date}-{slug}/ containing task.md; a new row in routing.db artifacts table with status='open'; session context ({slug}, {log_dir}, {project_id}) populated for downstream skills.

Hands off to

idea-first — determines task type (product / feature / fix) and routes to the correct branch (habit-first / arch-first / audit-first).

---

Step 1 — Determine project

Early return — if {project_id}, {project_path} and {project_name} are already set in session context (e.g. after /go-start) — use them without re-asking. Output confirmation with override option:

Using project from go-start: {project_name}
Override? (Enter / no — continue with this, or number from list)

1. {project 1}
2. {project 2}
...

Response	Action
Enter, "no", empty	Use the set {project_id} — go to Step 2
Number from list	Set new {project_id} + {project_path} + {project_name} — go to Step 2

Standard flow — if {project_id} is NOT set (go-fast called without go-start):

Read the projects config and show only status: active projects:

Which project is this task for?

1. {project 1}
2. {project 2}
...

Enter number:

Wait for answer. Save chosen project id and path as session context: {project_id}, {project_path}, {project_name}.

---

Step 2 — Receive task

If task description was provided inline after /go-fast — use it directly. If not provided — ask What are we doing? and wait.