agentsclimarketplace

Octospec init

Skill meo9805/mininglamp-oss-octo-spec/templates/octospec-init/.claude/skills/octospec-init

[Mirror/Mininglamp-OSS] Mininglamp-OSS/octo-spec — Git-native AI coding engineering standard: shared specs, tasks, and project memory in your repo.

Install
npx -y skills add meo9805/mininglamp-oss-octo-spec --skill octospec-init

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Use the FIRST time you bring the octospec engineering standard into a repo that does not have it yet — to onboard octospec / initialize octospec into a fresh checkout. Triggers on requests like "onboard octospec", "initialize octospec", "set up octospec here", "add the octo-spec standard to this repo", 在这个仓库接入 octospec, 启用 octo-spec 标准, 初始化 .octospec。 This is a one-time接入引导: copy the template, pin the global version, run the sync script, confirm the agent-instruction block landed, and self-check with lint. Once the repo already has a working `.octospec/`, stop using this skill — the day-to-day 4-phase flow is owned by the octospec-workflow skill instead.

SKILL.md

6.0 KB, ~1.4k tokens by cl100k_base, as published. Nobody here has run it

octospec-init (onboarding)

This skill is the one-time接入引导 for the octospec engineering standard. Run it when a repo does NOT yet carry .octospec/ and you want to add it. There is no onboarding CLI subcommand or flag to invoke — onboarding is simply the handful of real shell steps below, run by hand.

Relationship: init = one-time onboarding (this skill). Once .octospec/ exists and syncs cleanly, day-to-day work hands off to the octospec-workflow skill (the runtime 4-phase flow: Plan, Implement, Verify, Finish). The two do not overlap — init wires the repo up, workflow drives changes afterward.

When to run this

Run it when:

  • the repo has no .octospec/ directory yet, and
  • you want this repo to follow the octo-spec shared standard.

Do NOT run it if .octospec/ already exists and octospec-sync.sh succeeds — that repo is already onboarded; switch to the octospec-workflow skill.

Steps

1. Copy the template skeleton

Copy templates/octospec-init from an octo-spec checkout into .octospec/ at the root of the target repo. This carries the rules index, task/journal scaffolding, the .claude/ commands + skills, and its own scripts/ (so the synced repo holds the sync tooling itself).

cp -r <path-to>/octo-spec/templates/octospec-init .octospec

2. Pin the global version and fill in metadata

Edit .octospec/manifest.yaml:

  • Pin the global ("constitution") version you inherit: inherits: octo-spec@<semver> — use the exact version of the octo-spec checkout you are syncing from. Read it from that checkout's VERSION file (cat <path-to>/octo-spec/VERSION) rather than hardcoding a number here, so this instruction never drifts when octo-spec bumps its version. For example, if VERSION says 1.2.0, set inherits: [email protected]. The pin must match the GLOBAL_SRC checkout's VERSION exactly or octospec-sync.sh fails the version assertion. The template manifest already ships pinned to this checkout's version, so when you sync from the same checkout no edit is needed.
  • Set tier (default repo — the global layer lives in octo-spec itself).
  • Set owner to the team or person responsible for this repo's .octospec/.

3. Sync

Run the sync script with GLOBAL_SRC pointing at a checkout of octo-spec at the pinned version. GLOBAL_SRC is mandatory: if it is unset the script prints guidance and exits 1.

GLOBAL_SRC=/path/to/octo-spec ./.octospec/scripts/octospec-sync.sh

This vendors the pinned global rules into the git-ignored cache .octospec/_global/ (the script adds _global/ to .octospec/.gitignore automatically), writes the shared agent-instruction block into the agent-instruction files present in the repo, AND materializes the repo-root scaffolding that tools only discover at the root:

  • copies .octospec/.claude/ to the repo root .claude/ so Claude Code finds the slash commands (/octospec-plan, /octospec-go, /octospec-check, /octospec-finish) and the workflow skill, and
  • copies .octospec/.github/PULL_REQUEST_TEMPLATE.md to .github/ so GitHub applies the PR template (the body the Finish phase pre-fills).

This step is install-if-missing: any .claude/ or .github/ file you have already customized at the root is left untouched, and re-running sync is idempotent. Commit the materialized root .claude/ and .github/ so teammates get them on a plain git pull.

4. Confirm the agent-instruction block landed

The synced block is delimited by whole-line markers <!-- octospec:begin --> / <!-- octospec:end --> in each agent file. Sync behavior:

  • CLAUDE.md and AGENTS.md are the two default entry points — whichever is missing is bootstrapped (created) so both Claude Code and Codex get the block.
  • GEMINI.md / QWEN.md are only touched when they already exist; they are never force-created.
  • Everything outside the markers (and the file's line endings / trailing newline) is preserved; a malformed marker state makes sync refuse that one file rather than risk clobbering hand-written content.

Open one agent file and confirm the octospec:begin/octospec:end region is present.

5. Self-check with lint

Run the OKF conformance lint once, from the repo root of the target repo, using the lint script in your octo-spec checkout (the same GLOBAL_SRC you synced from in step 3). Unlike octospec-sync.sh, the lint script is not vendored into .octospec/scripts/ — it is a one-time onboarding self-check, so it is run from the octo-spec checkout rather than copied into every repo.

GLOBAL_SRC=/path/to/octo-spec   # the checkout you synced from in step 3
"$GLOBAL_SRC/scripts/octospec-lint.sh" .

Exit 0 means the knowledge units conform. The linter recurses from ., so it picks up this repo's .octospec/rules/ (it scans OKF knowledge units under global/, */rules/, tasks/, and journal/; it does not inspect skill files, so this skill itself is out of scope).

After onboarding

Once the steps above pass, this repo is onboarded. Hand day-to-day coding back to the octospec-workflow skill, which runs the 4-phase flow for each non-trivial change. Re-run step 3 (sync) any time you bump the pin in manifest.yaml — it is idempotent.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 0 of the 12 instructions most quality gates skills give in ~1.4k tokens

Counted across 1,195 of the 2,094 authors here whose files we hold, read 2026-08-07

  • Read the output and check the exit codein 54 of 1195, across 14 files
  • Verify requirements using a line-by-line checklistin 53 of 1195, across 12 files
  • Identify the verification command proving the claimin 51 of 1195, across 12 files
  • Run the full verification commandin 50 of 1195, across 11 files
  • Verify output confirms the claimin 49 of 1195, across 12 files
  • Check version control diff after agent delegationin 46 of 1195, across 6 files
  • State claim with evidencein 44 of 1195, across 4 files
  • Run the test suitein 33 of 1195, across 26 files
  • Keep state in memory by defaultin 27 of 1195, across 6 files
  • Make prototype runnable with one commandin 26 of 1195, across 5 files
  • Produce a verification reportin 25 of 1195, across 14 files
  • Detect the package manager from lockfilesin 24 of 1195, across 5 files

Said here and by no other author read

  • copy the template skeleton to target repo root
  • pin the inherited global version in manifest file
  • set tier and owner in manifest file
  • run the sync script with global source path
  • confirm agent-instruction block exists in agent file
  • run the lint script from the global source checkout

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.