| name | implement |
| description | Skip planning, query schema, implement directly. Use when you want code not plans. Say "/implement [feature description]" to go straight to building. |
Implement Directly
No plans. No discovery phases. Build immediately.
Rules
- Do NOT write a plan document. Do NOT enter plan mode. Start coding.
- If you need schema, query it — then start coding immediately:
SELECT column_name, data_type FROM information_schema.columns
WHERE table_name = '<relevant_table>' ORDER BY ordinal_position;
- If you need to understand existing code, read 1-2 files — then start coding immediately.
- If unsure about ONE thing, ask ONE question — then start coding immediately.
- Build in small increments: implement → type-check → implement → type-check.
- Run
npx tsc --noEmit after each file change in the relevant app directory.
Process
- Read the user's feature description from the arguments
- Identify the 1-3 files that need changing (read them)
- If DB work: query schema first (see above)
- Start writing code immediately
- Type-check after each file
- Report what was built when done
Anti-Patterns (NEVER DO)
- Writing a plan file to
thoughts/shared/plans/
- Entering plan mode
- Asking more than one clarifying question
- Reading more than 3 files before starting implementation
- Proposing multiple approaches and asking the user to choose