plot
Official@plot-pm · Switzerland
Git-native planning workflow for software development by @quatico-solutions
Agent Skills by plot
Showing 12 vetted skills indexed across 1 GitHub repositories.
plot-sprint
Manage sprint lifecycle with MoSCoW prioritization and Git operations.
challenge-the-plan
Automate plan interrogation with structured questioning to identify vulnerabilities.
plot-reconcile
Identify and report Plot workflow drift and branch inconsistencies.
plot
Manage software development planning within a git repository.
plot-idea
Create a plan branch, plan file, and draft pull request in Plot.
tracer-bullets
Guide creation of thin vertical slices for system validation.
story-tracking
Track multi-session tasks using markdown files and project rules.
plot-approve
Merge approved Plot plan PRs and create implementation branches.
plot-release
Verify release readiness and collect changelog entries from delivered plans.
plot-deliver
Automate Plot workflow delivery with plan verification and branch status updates.
ralph-plot-sprint
Automate sprint iterations by reading Git repository state and orchestrating development workflows.
plot-reject
Automate plan transition from Delivered to Approved in the Plot workflow.
Frequently Asked Questions About plot
FAQPage SchemaWhat specific project management tasks does this system enable?▼
This system enables sprint lifecycle management, MoSCoW prioritization, and multi-session task tracking using markdown files. It facilitates plan interrogation to identify vulnerabilities, manages branch-based plan approvals, and generates release-ready changelogs directly from repository state.
Which personas benefit most from these planning capabilities?▼
Software engineering leads, technical project managers, and developers working in Git-centric environments benefit most. It is designed for teams requiring tight coupling between project planning documentation and actual code implementation branches to ensure synchronization.
What are the prerequisites for implementing this planning system?▼
Implementation requires an existing Git repository environment. Users must maintain project plans as markdown files within the repository structure to enable the system to read state, track branch inconsistencies, and orchestrate the transition of tasks from draft to delivery.