@lbk-open/super-spec
Spec-driven development toolkit for AI coding agents: end-to-end workflows, multi-agent coding and review, living specs, and engineering guardrails
Package details
Install @lbk-open/super-spec from npm and Pi will load the resources declared by the package manifest.
$ pi install npm:@lbk-open/super-spec- Package
@lbk-open/super-spec- Version
0.2.0- Published
- Oct 31, 2026
- Downloads
- 280/mo · 237/wk
- Author
- liyue2008
- License
- Apache-2.0
- Types
- skill
- Size
- 247.3 KB
- Dependencies
- 0 dependencies · 0 peers
Pi manifest JSON
{
"skills": [
"./skills"
]
}Security note
Pi packages can execute code and influence agent behavior. Review the source before installing third-party packages.
README
SuperSpec
English | 简体中文 · Apache-2.0 license
Portable Agent Skills for feature delivery, coding, root-cause investigation, independent review and OpenSpec-compatible living specs. One prompt bundle works with Claude Code, Codex, Pi and OpenCode; no workflow runtime engine to install.
Install from npm/Pi or a checkout
The established npm/Pi distribution is @lbk-open/super-spec; the source checkout
keeps the local package name super-spec. See INSTALL.md for Pi
package installation, local plugins and manual copies, with explicit platform/scope
consent. The Pi gallery entry and
previous npm release 0.1.1 establish the channel, not availability of 0.2.0: check
the registry's actual version before installing a particular release. Then request:
- Use ss-feature-workflow to implement this requirement.
- Use ss-coding-workflow in lite mode on this approved plan.
- Use ss-troubleshooting-workflow to investigate and repair this issue.
Install all 20 ss-* directories side by side, including ss-references and ss-guardrails. Project/global discovery changes require consent; workflows don't install dependencies or globally configure agents as a recovery shortcut.
How delivery works
One continuous owner investigates, plans, codes and fixes each shared boundary. Main coordinates and arbitrates; children inherit actual parent model. The owner uses focused behavioral RED -> minimum GREEN -> refactor/regression. Fresh read-only independent review precedes a single retained final full verifier. Missing review or real test failures block completion; accepted fixes return to the same owner with fresh impact review and retained revalidation.
Proposal plus applicable delta is complete/validated BEFORE proposal approval. Repairs first confirm evidence-backed root cause; restoring an unchanged promise may justify no-delta with authoritative evidence. Prebranch work uses a protected external staged mirror. Reuse short plans, materialize identical approved bytes, and archive/rebase before review. Complete required commits before review only with existing Git authorization; PR delivery must use the already proven committed identity, otherwise report local delivery. Review, full tests and delivery bind actual current inputs including HEAD/index/diff, not merely file bytes. Publication never commits, repairs or rebases the proven candidate.
Flags are invocation-only: --auto/-a completes eligible policy gates, never fabricated human approval; --decide/-d chooses bounded options but skips no gate. --worktree/-w and --no-worktree/-W select authorized workspace. Combined -adw/-daW are supported; conflicting -wW stops. Preserve flags, human/auto/pending gate state, scope and workspace through handoffs/recovery in one protected external checkpoint. Unknown live writers block replacement; no automatic CLI/model/protocol fallback.
Full ends at actual PR creation or honest local delivery under user restrictions; lite ends locally with identical quality. Neither permits automatic merge, deploy, release, destructive cleanup or new scope. Multi-repo coordination requires real native cwd/delegation/terminal-result capabilities and explicit dependencies.
Skill catalog
| Skill | Purpose |
|---|---|
| ss-feature-workflow | Requirement through proposal/spec gate and delivery |
| ss-coding-workflow | Approved plan through verified delivery |
| ss-troubleshooting-workflow | RCA gate through repair and delivery |
| ss-multi-repo-workflow | Dependency-aware repository coordination |
| ss-proposal | Architecture, API/UI contracts and applicable delta |
| ss-plan | Reusable short behavior/interface/test-intent map |
| ss-inspect | Report-only evidence-backed investigation |
| ss-coding | Continuous-owner TDD, review and retained validation |
| ss-code-review | Fresh read-only causal-impact review |
| ss-create-branch | Safe authorized workspace preparation |
| ss-create-pr | Publish only an already proven candidate |
| ss-cleanup | Separately authorized exact-path cleanup |
| ss-write-spec | Strict OpenSpec delta authoring |
| ss-archive | Authorized pre-review authoritative spec merge |
| ss-show-spec | Read current capability specs |
| ss-trace-spec | Trace requirements to source |
| ss-list-changes | Read active/archive change inventory |
| ss-reverse-spec | Derive baseline specs from actual source |
| ss-guardrails | Shared safety/quality and language checks |
| ss-references | Shared policy/templates, not a standalone workflow |
Documentation and validation
- Workflow order and flags
- Roles, waiting and recovery
- Workspaces and multiple repositories
- Living specs · Guardrails
- Architecture · Security · Changelog
- Checkout only:
AGENTS.md(repository guide),RELEASING.md(release boundaries)
The npm bundle includes skills, documentation, local plugin manifests and the Codex
icon, not Git history, repository instructions, tests or release tooling. Use a full
repository checkout for development and release work; the existing GitHub v0.2.0 tag
is not the repaired npm candidate's source identity (see checkout RELEASING.md).
Repository validation uses ./scripts/validate.sh in that checkout; Node runs
static prompt-contract and weakening tests, not a live agent/native execution proof. Workflow execution
needs no Node helper. Native discovery/installation and host behavior require their
own authorized verification; missing tools are disclosed, never called passes.