okhp3-project-compass
Point at a project folder, git clone, or repository and establish or refresh its purpose, vision, mission, goals, and task tracking from evidence. Starts with a detection phase choosing Mode A, a GitHub-backed repo tracked through milestones, issues, sub-issues, labels, and releases via the gh CLI, or Mode B, a plain folder tracked entirely in files. First run infers intent from README, docs, ADRs, commits, TODO markers, and structure, then scaffolds a charter, an objectives-to-tasks decomposition, and machine-readable tracking with stable IDs. Later runs reassess progress, mark work done, blocked, or abandoned with evidence, surface new or changed goals as scope drift, flag orphaned and stale work, and emit a delta report. Also activate for "what is this repo even for", "is this project still on track", "did anything change since last time", scheduled or unattended check-ins, and projects with no tracking artifacts. Handles monorepos, content-first repos, and folders with no git histo
Target: Software development & testing. Automatically collected · unverified.
Excerpt from the author’s documentation
Extracted from a fixed version of SKILL.md in its original language. This is the author’s documentation; installation, compatibility and runtime results have not been verified by this site.
Read the original English text
Topics in the source
- okhp3-project-compass
- Scope
- Related skills
- Phase 0: detection, always first
- Mode A: GitHub-backed
- Mode B: plain folder
- One data model, both modes
- Operating contract
OverKill Hill P³ · overkillhill.com · github.com/OKHP3 Compass answers two questions about a folder. First time: what is this project for, and what is it trying to achieve. Every time after: what moved, what stalled, what changed shape, and what quietly died. Before either, it answers a third: where does the tracking actually live. A GitHub clone already has milestones, issues, and releases, so Compass uses them rather than building a parallel tracker. A plain folder has none of that, so the file layer carries everything. -- | In scope | Out of scope | |---|---| | Detecting whether a folder is GitHub-backed and branching accordingly | Guessing at ambiguous evidence; ambiguity resolves to the safe local mode | | Inferring purpose, vision, mission, goals, non-goals, success criteria from evidence | Inventing intent the evidence does not support | | Reading and planning GitHub milestones, issues, sub-issues, labels, releases through gh | Destructive or unauthorized GitHub writes, deletions, or scheduled pushes | | A committed file layer that works offline in both modes | Duplicating full issue bodies into the repository | | Reassessing status against commits, files, docs, issues, and
This is an excerpt. Refer to the complete source and its current requirements.
- Source repository
- OKHP3/skillz
- Source file
- universal/okhp3-project-compass/SKILL.md
- Fixed revision
- 7b187777d42ab7bc7bab1e5f2c940cd3139ecebf
Sources and evidence
This record was collected automatically. Its documentation, suitability and runtime behavior have not been manually verified.
Author: OKHP3/skillz · original repository metadata. Documentation review: Not reviewed. Last source check: 2026-11-10T10:00:55.873Z.
Categories are inferred from names, descriptions and paths. They do not establish compatibility.
License and attribution
MIT. Third-party content and copyright remain with their authors. Refer to the original license and terms.
Original license ↗Synchronization, copying and user-reported success do not mark a resource as runtime-tested.
Limitations and notes
- Collecting metadata does not mean this site has installed, adapted, runtime-tested or security-reviewed the resource.