acstack

Plugin acstack in ac8318740/acstack. Commands read from the repo's manifest — today.

Skills (21)

• archive

  Close out a cleared map – one whose frontier is empty with no fog and no claims left – by verifying the durable residue, meaning what the effort leaves behind in tests, ADRs and the glossary, was extracted, then closing the root and disposing of the nodes per workflow.maps.persist. Invoke when a map

• bridge

  Set up, diagnose, and operate the Playwriter bridge – the reverse-SSH setup that lets a coding agent on a Linux VM drive a real Chrome browser on a user's Windows laptop. Any bridge work spans two devices, so this skill routes you to the right platform-specific runbook and establishes the handoff co

• browser-verify

  The frontend skill. Before a UI edit it loads design context and the generic UI rules; after the edit it measures the rendered page with the bundled measure.js, checks behavior in headless Chrome through agent-browser, and runs a judge only when hierarchy or the primary action changed. Use whenever

• commit

  Create git commit(s), running the clean-context pre-commit review first for nontrivial changes, with proper pre-commit hook handling, MECE commit messages, safe staging, the design-token refresh, and a prose lint. Invoke whenever work is about to be committed – the user asked to commit, or told you

• compact-and-continue

  Anchor the session's load-bearing state so it survives an imminent context compaction, then hand the user a /compact line steered at the work. Writes only what nothing on disk holds – the next action, decisions already made, blockers, file ownership – and references everything else. Invoke before co

• design-doc

  Author a design doc on a map and review it through a live local or SSH connection that saves comments for the agent and answers back to the map.

• explore

  Enter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Invoke when the user signals they want to think rather than build – thinking out loud, weighing options, asking what if, or saying they are not ready to start yet. Explore mode never wri

• fix

  Find the root cause of something broken, then route the fix. Use when something is broken, behaves wrongly, or the user reports a bug. It reads the integration points before touching code, names the root cause rather than the symptom, and pauses when the fix spreads. Size is not implied: the fix the

• grilling

  Interview technique for settling open decisions in rounds. A round asks the whole frontier – every question whose prerequisites are settled – numbered, each with a recommended answer, then recomputes and repeats. Use whenever decisions need a human and requirements are foggy, with or without a map.

• handoff

  Hand the current work to a visible agent – a new one running in its own pane, or one already running. Writes only what nothing on disk holds – the next action, decisions already made, blockers, file ownership – and references everything else. Invoke when the user asks to hand work over or to spin th

• host

  Declare the dev setup of the machine you are on – which agent orchestrators are installed to host terminal panes and git worktrees, which browser-verification modes work here, and the optional extras. Interviews you for every axis and writes the answers to the ACStack CLI's global config under host.

• implement

  Implement clear requests with adaptive testing and verification under the shared Implementation discipline in orchestrator/AGENTS.md. A map is a stored graph of question and work nodes. Claims afk nodes – away from keyboard, meaning nodes an agent settles alone – from the map frontier, the nodes rea

• map

  The entry point for planned work. A map is a graph of question and work nodes. Charts one if none exists – an opening grill, meaning a round of interview questions, that fixes the destination and surfaces the fog, meaning what cannot yet be stated precisely – and works the frontier, the nodes ready

• new-worktree

  Create a git worktree branched off origin/dev (or origin/main) – through the orchestrator hosting this session, otherwise plain git under .claude/worktrees – then change cwd into it and continue the task there. Use whenever the user says \"create a worktree\", \"new worktree\", \"spin up a worktree\

• pre-commit-review

  Clean-context review of uncommitted changes before commit. Collects the diff and the requirements, launches a `reviewer` agent that sees only those, then the author filters its findings against what the user asked and fixes the ones that stand. /acstack:commit invokes it for nontrivial changes not y

• record-context

  Write durable records when a decision lands – an architecture decision record (ADR), a short file stating one decision and why, if the decision is hard to reverse and surprising and a real trade-off; a glossary entry if a term got settled; both, or neither. Invoke after a map node resolves or after

• setup

  Set up ACStack in a project, and change how an already configured project is set up. With no project.yaml in the project folder it detects the project type, writes the config and offers browser verification. With one already there it leads with the health check, then offers to fix each row that fail

• teardown-worktree

  Retire finished git worktrees – move the orchestrator's pane back to the main repo workspace, remove the checkouts, delete the merged local and remote branches, and offer to clean rebuildable build outputs in worktrees that stay. Scans the whole repo, not just the current worktree. Use whenever the

• terminal-workspace

  Install and configure the optional terminal workspace, which runs several coding agents side by side in one terminal. It installs five tools the user drives – herdr, gh-dash, diffnav, lazygit and harlequin – plus five that support them, two helpers of ACStack's own, and the pi coding agent with ACSt

• visual-docs

  Structure documentation around the reader's questions and the relationships being explained. Use for documentation, architecture, workflows, and explanations that need more than a short direct answer. Add diagrams when they clarify those relationships.

• writing

  Apply ACStack's shared communication standard to durable artifacts, including decisions, map nodes, handoffs, documentation, and pull request bodies. Read before writing or editing them.

Subagents (4)

• frontend-verifier

  Frontend verification agent. Runs the browser-verify skill's measure, behavior, and judge steps on final frontend code in headless Chrome through agent-browser, and keeps the project's verification memory current. Runs after required static and design gates pass.

• investigator

  Read-only investigator. Answers one bounded question about a codebase or source, keeping raw discovery out of the parent's context, and reports findings with evidence.

• reviewer

  Clean-context reviewer. Sees only the diff and the requirements, reviews behavior, design, coverage, and failure handling, and returns findings for the author to filter. Read-only. Owns completion checks only when explicitly assigned; browser verification belongs to frontend-verifier.

• scope-worker

  Owns one independent slice of a larger effort in Team mode. Implements and tests its scope in its own checkout under the shared Implementation discipline, then reports for the lead to merge and verify.

Hooks (8)

• SessionStart

  bash "${CLAUDE_PLUGIN_ROOT}/hooks/communication-standard.sh"

• SessionStart

  bash "${CLAUDE_PLUGIN_ROOT}/hooks/session-start.sh"

• SessionStart

  bash "${CLAUDE_PLUGIN_ROOT}/hooks/session-start-handoff.sh"

• SessionStart

  bash "${CLAUDE_PLUGIN_ROOT}/hooks/context-pressure.sh"

• SubagentStart

  bash "${CLAUDE_PLUGIN_ROOT}/hooks/communication-standard.sh"

• Stop

  bash "${CLAUDE_PLUGIN_ROOT}/hooks/context-pressure.sh"

• PreToolUse

  node "${CLAUDE_PLUGIN_ROOT}/hooks/read-guard.mjs"

• UserPromptSubmit

  bash "${CLAUDE_PLUGIN_ROOT}/hooks/ac-writing-style-reminder.sh"

Similar plugins