Soju06

Implement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or work through tasks.

Archive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete.

Archive multiple completed changes at once. Use when archiving several parallel changes.

Continue working on an OpenSpec change by creating the next artifact. Use when the user wants to progress their change, create the next artifact, or continue their workflow.

Enter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use when the user wants to think through something before or during a change.

Fast-forward through OpenSpec artifact creation. Use when the user wants to quickly create all artifacts needed for implementation without stepping through each one individually.

Start a new OpenSpec change using the experimental artifact workflow. Use when the user wants to create a new feature, fix, or modification with a structured step-by-step approach.

Guided onboarding for OpenSpec - walk through a complete workflow cycle with narration and real codebase work.

LLM knowledge cutoff compensator — knowledge corrections for breaking changes and API drift. Covers: renamed packages (shadcn-ui→shadcn), changed APIs (z.string().email()→z.email()), new config formats (.eslintrc→eslint.config.js), current model IDs, Apple platform changes. Versions are NOT cached — always verify via package manager. Useful for: install, create, scaffold, upgrade, migrate, latest, version, dependency, shadcn, tailwind, vite, zod, eslint, react, next, svelte, nuxt, django, fastapi, pydantic, ruff, uv, claude, gpt, gemini, openai, anthropic, deepseek, qwen, llama, mistral, kimi, minimax, glm, node, bun, python, typescript, macos, xcode, swift, swiftui, supabase, npm, pip, cargo, package.json, pyproject.toml, requirements.txt.

Project code conventions reference. Covers typing, structure, DI, testing, and anti-pattern rules for module implementation.