Overview

PactKit provides 11 commands as workflow entry points. Six former utility commands (trace, draw, doctor, status, review, release) are now skills — embedded into the PDCA commands and auto-invoked at the right moment.

Role-Based Command Guide

Choose commands based on your role in the team:

PDCA Core Commands

/project-clarify

Surface ambiguities before planning. Standalone command or auto-invoked by Plan.

/project-clarify "Add user authentication"

Runs: ambiguity detection → structured questions (Scope, Users, Constraints, Scale, Edge Cases, Non-Goals) → clarified brief output. The brief can be fed directly into /project-plan.

/project-plan

Analyze requirements and produce a Spec.

/project-plan "Add user authentication with OAuth2"

Runs: Init Guard → Clarify Gate (auto-detects ambiguous input, generates questions) → visual scan → logic trace (via pactkit-trace skill) → design update → Spec creation (with Spec Lint self-check) → Board entry.

/project-act

Implement code per Spec using strict TDD.

/project-act STORY-001

Runs: read Spec → Spec Lint Gate (structural validation — blocks on errors) → Consistency Check (Spec ↔ Board ↔ Test Case alignment, advisory) → detect stack → write tests (RED) → implement (GREEN) → lint check → verify suite.

/project-check

Run a comprehensive QA audit with structured security checklist.

/project-check

Runs: 8-item security checklist (SEC-1 to SEC-8, PASS/FAIL/N/A) → code quality scan → test case gen → layer decision → execution → Spec alignment → verdict. SEC-1 through SEC-5 failures are classified as P0 Critical. Includes pactkit-review skill for PR code review scenarios.

/project-done

Finalize delivery with regression gate and conventional commit.

/project-done

Runs: cleanup → regression gate → lint gate → HLD consistency check → rules.md invariants refresh → board hygiene → archive → snapshot verification → commit → Auto-PR (structured PR body from Spec + test results, with user confirmation). Includes pactkit-release skill for version release scenarios.

Automation

/project-sprint

Run the full PDCA cycle in one command.

/project-sprint "Add user authentication"

Orchestrates Plan → Act → Check → Done automatically using a multi-agent team. Requires the Opus model.

/project-hotfix

Fast-track fix that bypasses the full PDCA cycle.

/project-hotfix "Fix typo in README"

Skips TDD and Spec creation. Suitable for typos, configuration changes, and minor fixes.

Lifecycle

/project-design

Greenfield product design for new projects.

/project-design "Build a task management app"

Generates PRD, decomposes into Specs, and populates the Sprint Board. Uses pactkit-draw skill for architecture diagrams.

/project-init

Initialize project scaffolding and governance structure.

/project-init

Sets up the directory structure, architecture graphs, initial governance files, and project-level instructions. For Claude Code: .claude/CLAUDE.md. For OpenCode: ./AGENTS.md + opencode.json with permission and MCP config.

/project-release

Version release workflow: snapshot, archive, and Git tag.

/project-release

Runs: version bump → architecture snapshot → story archive → Git tag creation. Uses pactkit-release skill for snapshot and archive operations.

/project-pr

Push branch and create a pull request via gh CLI.

/project-pr

Runs: push current branch to remote → create pull request with structured body (Summary + Test Plan) derived from Spec and test results. Requires gh CLI to be installed and authenticated.

OpenCode Model Routing

When deployed to OpenCode, commands include a model: field in their frontmatter for automatic model routing:

This is configurable via command_models in pactkit.yaml. Model shortnames (sonnet, opus, haiku) are automatically resolved to full provider/model-id format from your opencode.json provider configuration.