Persistent, per-objective working memory for coding agents — one standalone git "notepad" repo per objective that survives context compaction, spans multiple code repos from a single session, keeps an append-only journal, and mirrors into an episodic memory index. Ships as a Claude Code plugin (hooks + skills +…
Persistent, per-objective working memory for coding agents — one standalone git notepad per objective that survives compaction, spans multiple code repos from a single session, keeps an append-only journal, and mirrors into an episodic memory index. Evolves and supersedes handoff-auto.
Publish a deliberate, structured Handoff document for the current objective into the active notepad and force a git push so it syncs across machines. Use when wrapping a session, handing to a teammate or fresh agent, hitting a milestone, or asked to "create a handoff", "write a handoff", "checkpoint for next session"…
Create or refresh an agent-notepad — a per-objective working-memory git repo (one notepad per objective, grouped by name prefix) that survives context compaction and drives several code repos from one session. Runs a short interview (objective, code-repo paths, done-criteria), optionally gh repo creates the notepad…
Archive a completed or abandoned agent-notepad while keeping its journal history intact. Marks the notepad retired (SCOPE.md status + a final journal milestone), stops it from auto-loading and syncing on future sessions, and preserves the append-only sessions/ history and handoffs for later recall — it never deletes…
Review architectural changes for coupling, blast radius, and long-term impact. Use when evaluating system design changes, cross-service dependencies, API changes, or infrastructure modifications. Triggers on "architecture review", "impact analysis", "blast radius", "coupling review", "dependency analysis", "breaking…
Upload or download large files to/from a Coder CDE workspace using the coder CLI. Use when transferring files, directories, build artifacts, datasets, or binaries to a Coder workspace, when rsync -e "coder ssh" fails or desyncs, or when a copy over coder ssh hangs/corrupts. Triggers on "upload to coder", "copy files…
Analyzes any microservice codebase and generates a complete cold-start package — CLAUDE.md, custom skills, requirements template, development process docs, and onboarding guide. Works for any architecture. Use when setting up AI-assisted development for a new project. Triggers on "cold start", "set up AI development"…
Create high-quality Claude Code skills with proper structure, effective descriptions, and best practices. Use when creating a new skill, writing SKILL.md files, setting up skill directories, or asking how to make skills.
Proactively challenge implementation plans, architecture decisions, and design assumptions. Use when reviewing plans, designs, or technical decisions. Verifies claims via web search, cross-references documentation, identifies risks and gaps, and surfaces hidden assumptions. Activates automatically when evaluating…
End-to-end Dark Factory build orchestrator: intent to shipped software via the df- stages, test-first, adversarially verified, autonomous in dev/non-prod, documented as stage docs plus tickets. Triggers on "build this the dark factory way", "run a dark factory build", "take this spec to done end-to-end".
Autonomous development and integration testing from a requirements doc. Implements everything — database changes, contracts, handlers, configuration — then tests against real infrastructure (dev DB, dev RabbitMQ). Verifies by emitting events, checking DB state, reading logs, and checking error tables. Triggers on…
Run the adversary gate: assess whether presented evidence proves a promise was kept, without redoing the work and never trusting a self-report. Use before trusting any "done/passing" claim, PR, or handoff. Triggers on "adversary review", "verify", "gate", "assess evidence", "is this really done".
Record a narrated, captioned product walkthrough video of a web app end-to-end with no human in the loop — synthesized voice-over, a real browser driven with a visible cursor, burned-in captions, assembled to mp4. Works against a public website or an authenticated app (Clerk session-ticket, or any Playwright…
Dark Factory Stage 0.5 — scaffold a repo's in-repo agent inner-loop substrate (read-first context store + single-responsibility agents + checkable hand-off contracts + commit gate) from the proven template, populate it from the real codebase, and verify it. Use when bootstrapping a repo for DF work, running a DF…
Feature Architect. Designs the minimal-impact implementation for a new feature or a confirmed fix — files to touch, contracts, migrations, risks, test plan — without writing code. Consumes a requirement (or a Root Cause) and the context store; produces a Design Spec for the implementer. Use for "how should we build…
Code Implementer. Writes the actual code changes for a Design Spec — only after requirements are clear. Implements per the design, keeps the diff minimal, and updates contracts/migrations consistently. Use for "implement this", "make the change", once a plan/Design Spec exists. Does not invent scope.
System Investigator (read-only). Traces a flow across ANY service, DB, queue, API, or infra component and gathers the evidence around a symptom or change area. Does NOT decide the root cause and does NOT edit code — it produces a structured Evidence Bundle for the root-cause-analyzer or feature-architect. Use first…
Knowledge Keeper. Maintains the context store (SERVICE-MAP, FINDINGS, DECISIONS) and per-service CLAUDE.md so analysis is done once and reused — preventing repeated investigation and keeping token use low. Records confirmed root causes and decisions; compresses; fixes stale docs against source. Use for "remember…