canopus

Solid

The engineering standard for building anything non-trivial in this workspace: seven numbered steps, with the operator's two moments as steps 4 and 7. Bare `/canopus` prints the seven steps and where the operator's two moments sit in them. Subcommands are thin: `note` writes the slice's committed record, `check` runs the four clauses a CI step runs identically, `probe` measures whether a contract's redness means anything. Use for any change worth a plan. Skip typo fixes and config-only edits.

AI & Automation 11 stars 1 forks Updated 2 days ago Apache-2.0

Install

View on GitHub

Quality Score: 82/100

Stars 20%
36
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Canopus The standard for building anything non-trivial here. Seven steps, two of them the operator's own. Every mechanical part is built out of git, GitHub and pytest rather than re-implemented in Python. One shell command defeated 93 percent of the retired version's hand-built prevention surface. **The one thing this exists to prevent:** a contract too weak to decide anything, passing as one that decided. Across all 62 prior records a contract was never once weakened after the fact, and was born too weak thirty times. The green to distrust is the one no wrong implementation was ever made to fail. ## Bare `/canopus` — the seven steps Nothing is run. Show the agenda below and name the step the work in hand is at. Read that position from the conversation, never from the disk. Only steps 4 and 7 leave a trace in this repository, so a position read off it is a guess dressed as a measurement. ## The seven steps The agenda has exactly one definition, `scripts/utils/canopus_steps.py`. This file may summarise it and may never renumber it. ``` 1. Define the Value 2. superpowers:brainstorming -> scope document 3. superpowers:writing-plans -> plan 4. /scrutinize the plan, apply every finding -> the operator's commit 5. superpowers:subagent-driven-development -> implementation 6. /scrutinize --relentless, apply every finding 7. Production ``` Steps 4 and 7 are the operator's. The seven steps fall into four acts: - Act 1, steps 1 to 4. Nothing ...

Details

Author
mishahanin
Repository
mishahanin/heading-os
Created
2 months ago
Last Updated
2 days ago
Language
Python
License
Apache-2.0

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

ops-automation

Production scripting and ops automation — shell scripts, config-management playbooks and roles, scheduled jobs, monitoring checks. Use when writing or reviewing automation that runs unattended, repeatedly, or against a fleet, when a change touches high-impact system surfaces, and when planning patching or provisioning runs.

0 Updated 1 months ago
voklab
AI & Automation Listed

blueprint

Turn a one-line objective into a sequenced construction plan — decompose into steps, find the dependency order, mark what can run in parallel, name the verification gate. Use before multi-step builds.

28 Updated today
jedbjorn
AI & Automation Listed

vibecodeprotocols

TDD methodology for Claude Code: the orchestrator runs VCP's internal contract and Sonnet 5 (low effort default) implements via 5 role-persona subagents (Test-Engineer/Builder/Refactor-Engineer/DOCS/CHORE — none certifies its own gate). Paperclip-style AI-company layer: org chart (.vibe/COMPANY.md), goal ancestry per task, atomic task checkout for parallel builds, append-only audit log (.vibe/AUDIT.md), lightweight budget policy w/ 3-retry hard stop. Auto-routing triage skips full pipeline for trivial changes. .vibe/ persists memory incl. LESSONS.md (Reflexion-schema, confirm-gated, deduped, retire-not-delete cross-project error memory) + optional local mirror. Final phase = native verify+risk-tiered simplify+security+risk-modulated adversarial+tests+receipt-gated commit/push/merge+backups+reflect+lessons-confirm. Hard gate: no red test = no code.

0 Updated 1 weeks ago
santischurmann