A Russian-language checkpoint and session-closing procedure that records the verified state of ongoing work in a HANDOFF file. A HANDOFF file is a written task record containing what is done, what remains, blockers, statuses, and journal entries.
An architect for large software tasks who first turns requirements into a written specification and then divides the work into self-contained task packets. It also records dependencies and suggested ownership.
An executor for one task packet under the pf-do process, a workflow for completing software tasks with explicit evidence and statuses. It works within the packet's defined scope.
A reviewer for task packets and technical specifications. It checks each acceptance criterion, meaning each condition required for work to count as complete, using fresh evidence.
An autopilot workflow that completes approved software specifications by assigning tickets to smaller helper agents. A specification is a written description of what should be built; tickets are individual work items.
A change-of-direction skill for projects that are already being built. It traces a new decision through the specification, work items, and completed or unfinished work.
A workflow retrospective skill that reviews journals, task records, and Git activity across projects. It looks at how work progressed and where processes could improve.
An interview-based specification skill for large tasks or new projects. It asks for the important decisions one at a time and records the answers in a SPEC.md file.