Initialize a spec-driven development workspace for the current project. Creates a .spec/ directory that will hold three files:

• requirements.md: User stories, acceptance criteria (EARS format)

• design.md: Architecture, diagrams, implementation approach

• tasks.md: Trackable checkbox tasks

• hooks/: Event-driven automation rules

Call this FIRST when user expresses intent to build, plan, design, analyze, or refactor.

Write content to one of the three spec files. Use this to create or update requirements.md, design.md, or tasks.md.

Read the content of one of the three spec files. Use this to review requirements, check design decisions, or see task status.

List all spec files with their status (exists, size, task count).

Mark a task as done or pending in tasks.md. Use this during implementation to track progress. The task is identified by matching its text content (case-insensitive partial match).

Get a summary of task completion status from tasks.md.

Register an automation hook for the spec workflow. Hooks define actions the AI should automatically perform when specific events occur. Events: on-requirements-confirmed, on-design-confirmed, on-tasks-confirmed, on-task-completed, on-implementation-done, on-spec-phase-change, on-user-request-change, manual

Example: when a task is completed (on-task-completed), auto-run update-task to mark it [x].

List all registered hooks with their event type and description. Use this to review what automations are active.

Remove a hook by name.

Get all hooks matching a specific event type. The AI should call this when an event occurs and execute the matching hooks' instructions. For example, after completing implementation of a task, call run-hooks with event "on-task-completed" to find and execute all relevant hooks.