Skip to content
HN On Hacker News ↗

PlanWright — The control plane for autonomous software labor

▲ 9 points by dudemanAtl 1mo ago HN discussion ↗

Pangram verdict · v3.3

We believe that this document is fully AI-generated

99 %

AI likelihood · overall

AI
0% human-written 100% AI-generated
SEGMENTS · HUMAN 0 of 3
SEGMENTS · AI 3 of 3
WORD COUNT 888
PEAK AI % 99% · §1
Analyzed
Jul 13
backend: pangram/v3.3
Segments scanned
3 windows
avg 296 words each
Distribution
0 / 100%
human / AI fraction
Verdict
AI
Pangram v3.3

Article text · 888 words · 3 segments analyzed

Human AI-generated
§1 AI · 99%

The Control Plane for Agent LaborYour coding agents got 10x faster. Your pipeline didn't.Speed moved to the middle and left the ceremonies behind. Planwright inverts the two that are still human-paced: it turns your chaos — transcripts, decks, email, Slack — into objectives, and triages acceptance so you rule only on what needs judgment. Planning and acceptance finally move at agent speed, and every ruling is signed.Claude Desktop · MCP› planwright_list_objectives↳ “Reposition homepage” · scheduled↳ “SOC 2 export bundle” · scheduled› planwright_claim_objective↳ claimed · agent run startedThe ProblemYou bought the agents.Where did the speed go?Coding used to be the bottleneck. Not anymore. Now the constraint is everything you didn't automate:PlanningA human hand-typing tasks at UI speed to feed machines running thousands of times faster.AcceptanceA senior engineer reading pull requests one at a time — which is exactly where velocity goes to die.Make the middle free and infinitely fast, and the edges become the ceiling. That's not a tooling gap. It's Amdahl's law.The FixInvert the two ceremonies coding agents can't remove.Front bookendInvert planning: chaos in, objectives out.Your planning input was never tidy — it's meeting transcripts, decks, email threads, Slack. From inside Claude Desktop, Planwright synthesizes that raw signal into structured objectives with machine-checkable acceptance criteria. The old ceremony had a human write the plan and the tool record it. Planwright flips it: the agent drafts, you approve — at the speed of describing what you want.Back bookendInvert acceptance: triage, don't drown.When objectives complete, Planwright picks them up and triages acceptance in Claude Cowork — combing the plain, mechanical criteria and clearing what it safely can, then routing the critical, judgment-bound items to you. The machine doesn't accept; it sorts. You stop reading every diff and start ruling only on what actually needs a human, so your scarce judgment gets concentrated instead of flooded. Every ruling is signed.The Acceptance GateThe machine doesn't accept — it sorts.The state machine ensures a human rules on every judgment call before work reaches “done.” Mechanical criteria get cleared automatically; critical decisions route to you.

§2 AI · 99%

Your sign-off is the change-approval control point your SOC 2 auditor is looking for.ScheduledHumanHuman sets the objective and schedules it for agent pickup.In ProgressAgentAgent claims the work, plans, codes, and records diffs via MCP.AcceptanceHumanAgent requests acceptance. A human reviews the diff, tests, and signs off.DoneHumanHuman approves. The audit record is sealed and hash-chained.Every lane transition produces a hash-chained, cryptographically signed audit record. The chain is independently verifiable on the public trust page.How It WorksThree primitives. One throughput unlock.Turn chaos into objectives.In Claude Desktop, Planwright synthesizes your transcripts, decks, email, and Slack into structured objectives with machine-checkable acceptance criteria. You approve intent instead of hand-authoring tasks.Triage acceptance, don't drown in it.When objectives complete, Planwright combs the mechanical criteria in Claude Cowork and clears what it safely can, routing only the judgment calls to you. The machine doesn't accept — it sorts.Every ruling is signed.Machine-cleared throughput stays accountable: each human decision is a hash-chained record, not an ad-hoc PR read.The BoardObjectives flow. Agents execute. Humans approve.Backlog1Add webhook retry logicScheduled1Migrate auth to PKCE flowIn Progress2Implement ECDSA P-256 audit signingclaude-codeAdd RLS policies for workspacescursorAcceptance1SSE transport for MCP serverclaude-codeDone1Database schema v1codexHow It WorksFive steps. Zero busywork.01Write an objectiveDescribe the outcome you want. Not the steps. Not the implementation. A clear, atomic objective your agent can own end-to-end.02Your agent claims it via MCPClaude Code connects to your Planwright board, picks up scheduled objectives, and starts working. No copy-pasting tickets. No context-switching.03Agent plans, executes, requests acceptanceThe agent decomposes the objective, writes code, runs tests, and moves it to the acceptance lane. Every step recorded in the audit chain.04You review and sign offEvery acceptance is a cryptographic signature. Not a checkbox. A real approval with your identity bound to it.05Every step hash-chained and signedImmutable audit trail from objective creation to final merge.

§3 AI · 99%

SOC 2 evidence that writes itself.ComplianceSOC 2 auditors are raising the bar on AI-generated code.Under the 2026 Trust Services Criteria, auditors increasingly expect immutable, tamper-evident audit trails and documented change-approval controls for AI-driven changes. Most PM tools can't produce them. Planwright ships this as a core primitive — hash-chained, ECDSA P-256-signed, from the first objective to the final merge.Get StartedOne command. Every agent.No tokens. No config files to hand-edit. Run the install command — your browser opens for GitHub login, and you're connected.claude mcp add planwright --transport http https://mcp.planwright.tools/mcpZero-config. Run this command and your browser opens for GitHub login. The connection is cached for future sessions.1Run the connect command above2Log in with GitHub in your browser3Pick your workspace (if you have more than one)For CI and service accounts that can't open a browser, generate a static token in Settings → MCP Token after signing in. Audit records attribute to the token creator.Need more detail? Read the full Claude Code setup guide →PricingStart free. Scale when you're ready.Every plan includes the MCP server, audit chain, and board. Pay for seats and retention depth.Free$0For solo developers trying agent-native planning.Up to 3 seats1 project30-day audit retentionCommunity supportGet started freeTeam$15/seat/moFor small teams shipping with agents every day.4–10 seatsUnlimited projects1-year audit retentionPublic trust pageGitHub App integrationStart free trialMost popularBusiness$39/seat/moFor teams that need compliance out of the box.11–50 seatsUnlimited projects3-year audit retentionCustom domain trust pagePriority supportAdvanced analyticsStart free trialEnterpriseCustomFor organizations with regulatory requirements.51+ seats7-year audit retentionSSO / SAML (roadmap)SOC 2 attestation letter (roadmap)Dedicated supportCustom integrationsContact salesFAQQuestions teams shipping with AI ask.