making-things

Use when an active frontend, backend, or integration workstream must pause and record a sidecar HANDOFF.md.

Use when a paused frontend, backend, or integration workstream must resume from its sidecar TRACK.md and HANDOFF.md records.

Use when the user explicitly requests a complete Electron workflow rather than a small edit or one-stage request.

Use when the current host has dated WRITE_SUBAGENT: VERIFIED evidence and the user requests parent-supervised native-subagent TDD for one workstream task.

Use when a declared frontend, backend, or integration workstream has one READY task for parent-led sequential TDD.

Use when an approved Electron contract must split one feature into frontend, backend, and integration workstreams with TDD task records.

Use when an Electron failure or confirmed review finding can be reproduced and needs root-cause analysis, a minimal fix, and regression verification. Do not use for speculative cleanup, broad refactoring, initial review, or masking failures by weakening safeguards.

Use when an approved Electron PRD, architecture, and plan are ready for feature implementation across main, preload, renderer, shared code, services, or workers. Do not use for discovery, independent final review, speculative debugging, packaging approval, or publishing.

Use when Electron work adds or audits BrowserWindow privileges, preload APIs, IPC, filesystem, URLs, subprocesses, secrets, permissions, remote content, or CSP. Do not use as a substitute for a full product review, penetration test, feature implementation, or release authorization.

Use when an accepted Electron work item needs packaging configuration, versioning, signing/notarization readiness, artifact checks, update metadata, or a Windows/macOS/Linux release matrix. Do not use to publish, upload, or claim unrun platform builds.

Use when an independent context must assess an Electron task, diff, security boundary, tests, or release evidence before acceptance. Do not use for initial implementation, speculative rewrites, or fixes before findings are evidenced.

Use when an Electron work item needs test planning, unit or IPC coverage, preload contract tests, Playwright Electron E2E, multi-window checks, or packaged smoke evidence. Do not use to invent passing results, bypass a failing gate, or authorize release.

Use when a verified work item explicitly requires Git branch creation, intentional commits, non-force push, pull-request handoff, or authorized artifact delivery. Do not use outside a Git repository or to publish a formal Release without explicit authorization.

Use when an Electron work item needs product discovery, a PRD, scoped requirements, user flows, or acceptance criteria before architecture. Do not use for implementation, code review, debugging, packaging, or publishing.

Use when an approved Electron PRD needs architecture, process ownership, data flow, IPC contracts, stack decisions, migration, or rollback design. Do not use before PRD approval or for feature coding, independent review, debugging, or release execution.