All authors
Claude Skills by osteonlabs
github.com/osteonlabs15 skills0 installs0 views
- Bone InitScaffold a new BONE, the one governed knowledge repository for a project, from the scaffold this plugin ships, with its decay-check hook wired and a genesis commit. Use when starting OSTEON on a project, when someone says "set up a BONE", "start a knowledge repo" or "init OSTEON here", or when a project has no knowledge repository yet. NOT for operating an existing BONE (bone-onboard) or changing one (bone-curator). Read this file first; it runs one script.Votes: 0GitHub stars: 2
- Bone AdrAuthor, amend, or supersede a decision record in a BONE knowledge repository. Use when a durable or hard-to-reverse choice is being made, when someone says "we decided", "lock this in", or "write it up so we stop re-litigating", when an accepted record no longer matches what the running system does, or when a merged change silently suspends a decision. Covers numbering, the proposed/accepted/superseded lifecycle, and the amend-never-rewrite rule. NOT for seam schemas (bone-contract) or knowle...Votes: 0GitHub stars: 2
- Bone ContractCreate, version, or change the contract for a seam between two modules in a BONE knowledge repository. Use when two components start talking, when a wire format, field, unit, auth header, or failure behaviour is about to change, when one side is being built against the other's source instead of a written contract, or when someone asks "what does this return", "who owns this field", or "why did the payload change". Covers semver, the same-wave rule, and the registry index. NOT for decision rat...Votes: 0GitHub stars: 2
- Bone CuratorAudit a project's BONE knowledge base and evolve it through per-item human approval. Use when a session-start decay warning fires, when a decision locks or a state record is re-verified, when a skill reads stale, redundant, or missing, or when someone says "the skills are out of date", "audit the knowledge base", "is this still true", or "curate". Proposes ADD / UPDATE / REMOVE / MERGE / SPLIT and applies nothing without sign-off. NOT for writing a decision record (bone-adr) or a seam contrac...Votes: 0GitHub stars: 2
- Bone GitBranch, commit and change-request discipline for any BONE-governed project, parameterised by MANIFEST.yaml instead of hardcoded to one forge or tracker. Use when asked to "commit", "push", "open an MR", "open a PR", "start a branch", "land this", when a push is rejected or a branch has drifted, or when dirty work spans several concerns. NOT for judging a diff's content (bone-review), forge auth and connection mechanics (the project's T1 integration skill), or knowledge-base edits (bone-curato...Votes: 0GitHub stars: 2
- Bone OnboardCold-start procedure for a human or agent meeting a BONE-governed project, or returning after a gap. Gives the exact read order (L1, MANIFEST, L2 indexes, then only the relevant L4), separates what is currently true from what was once true, and ends in an orientation whose first action names the fact it depends on. Use when asked "get up to speed", "onboard me", "pick this back up", or a session starts in an unfamiliar repo. Makes time-to-first-correct-action collectable. NOT for the daily rh...Votes: 0GitHub stars: 2
- Bone ReviewReview a change against the project's own bar, derived from its BONE (L1 constitution, L2 decisions and state, L3 contracts and domain, L4 unit rules) not from generic best practice. Use on any diff before merge, as the self-review before a change is declared ready, and when asked "review this", "is this safe to merge", "what will a reviewer say". Also detects when a change invalidates a decision, a contract or a unit claim and routes it to bone-curator. NOT for branch and merge mechanics (bo...Votes: 0GitHub stars: 2
- Bone StandupThe operating rhythm of a BONE-governed project, kept per declared track. Use at the start of a session (brief), the end (debrief), for a weekly rollup or an on-demand status, and when asked "where were we", "what did we do today", "what is the status", or when picking a project back up after a gap. Owns the continuity journal that makes a dormant project restartable, drafts audience-aware updates, and routes blind spots to the owning role instead of guessing. NOT for deciding (bone-adr) or e...Votes: 0GitHub stars: 2
- Osteon CaptureCapture what a session learned about the way of working and route it, without ever writing a rule. Use the moment something fails, something is blocked before it lands, or a check passes on an input that must fail, and again at session end to test whether an observation has independent corroboration yet. Appends to a ledger that governs nothing, then nominates and stops. NOT for a project's own knowledge base (bone-curate-fast). Read the methodology register first.Votes: 0GitHub stars: 2
- Osteon FrameworkOwn the OSTEON framework that every project's BONE inherits from, with its taxonomy of framework things, the inheritance chain from specification and scaffold to instance, and the register of named methodologies. Use when a new project's BONE is started, when someone asks "where does this rule come from", "is this still conformant" or "is this a tool, a skill or a methodology", or when a way of working needs a name. NOT for papers, instruments or the corpus (osteon-research-unit), nor one ins...Votes: 0GitHub stars: 2
- Osteon Ossification Delivery TeachingTeach people outside the session what an ossification cycle delivered and where it stands, as a delivery, status or progress report rendered from one source into Markdown and PDF per audience, with headless screenshots and every claim graded by what proves it. Use when asked for a "delivery report", "status report", "progress report", "what changed and where to test", "what do we tell the client", or to announce a batch. NOT the session brief or journal (bone-standup), NOT the plan itself (os...Votes: 0GitHub stars: 2
- Osteon Ossification Plan ImplementorRun an ossification plan that has passed its gate, as ONE session that cuts lanes on shared surfaces and works them as parallel sibling subtasks, then carries finished work back into the plan. Use once a plan is calcified and building is about to begin, and whenever a lane finishes, stalls or discovers work the plan does not carry. Covers lane cutting, the parallel subtask shape, what may merge, and why a merge is not a completion. NOT the gate, which is `osteon-ossification-plan-starter`.Votes: 0GitHub stars: 2
- Osteon Ossification Plan StarterDecide whether an ossification plan may start, and get every open decision answered by asking the owner one clear question at a time rather than reporting that questions exist. Use when a plan is declared ready, when its author says it is complete, and when a plan has been running and its state is unclear. Covers the ten gate conditions, what input refuses each, and how to put a decision to a human so it can be answered in one line. NOT the plan itself, which an ossification planner owns, and...Votes: 0GitHub stars: 2
- Osteon Ossification Planner Project DailyPlan a multi-repository project's work as one dated cycle per day, held in the knowledge instance, and set the bar every task's definition of done must clear. Use at the start of a working day before opening any change request, when a merged change request needs marking done, and when a previous day's cycle is still open. One of the ossification planners, for a project planned daily. NOT the gate that decides whether a plan may start, which is `osteon-ossification-plan-starter`.Votes: 0GitHub stars: 2
- Osteon Single Session OssificationRun an ossification as ONE session with subagent osteoblasts, instead of several cooperating sessions signalling each other. Use when a large plan must be executed quickly and cheaply, with the session owning the plan, the merge and the verdict and delegating only the work. Covers the rules that made it deliver, the failure modes it removes, and the measured cost of the multi-session alternative. NOT the multi-session variant, which is `osteon-framework`'s Ossification entry.Votes: 0GitHub stars: 2