GitHub - kborovik/pilot-skills: Claude Code plugin marketplace — sdd (spec-driven dev) and gh (GitHub workflow) plugins · GitHub
/" data-turbo-transient="true" />
Skip to content
Search or jump to...
Search code, repositories, users, issues, pull requests...
-->
Search
Clear
Search syntax tips
Provide feedback
--><br>We read every piece of feedback, and take your input very seriously.
Include my email address so I can be contacted
Cancel
Submit feedback
Saved searches
Use saved searches to filter your results more quickly
-->
Name
Query
To see all available qualifiers, see our documentation.
Cancel
Create saved search
Sign in
/;ref_cta:Sign up;ref_loc:header logged out"}"<br>Sign up
Appearance settings
Resetting focus
You signed in with another tab or window. Reload to refresh your session.<br>You signed out in another tab or window. Reload to refresh your session.<br>You switched accounts on another tab or window. Reload to refresh your session.
Dismiss alert
{{ message }}
kborovik
pilot-skills
Public
Notifications<br>You must be signed in to change notification settings
Fork
Star
main
BranchesTags
Go to file
CodeOpen more actions menu
Folders and files<br>NameNameLast commit message<br>Last commit date<br>Latest commit
History<br>154 Commits<br>154 Commits
.claude-plugin
.claude-plugin
.claude
.claude
benchmarks/glyph
benchmarks/glyph
pilot-core
pilot-core
pilot-plan
pilot-plan
pilot-spec
pilot-spec
.gitignore
.gitignore
CLAUDE.md
CLAUDE.md
LICENSE
LICENSE
README.md
README.md
SPEC.md
SPEC.md
View all files
Repository files navigation
pilot-skills
Claude Code plugin marketplace. pilot-spec drives spec-driven dev, pilot-plan drafts the GitHub paperwork, pilot-core ships shared skills.
The bet
Consistency is the only quality that survives velocity.
Modern LLMs write code faster than any human can read it — and faster than the agent can stay coherent with itself. Vibe coding outruns spec-driven dev right up to the third feature that contradicts the first two. Multi-agent orchestration makes it worse: sub-agents race on shared files, tooling glues the diffs together, and the reasoning ends up scattered across N transcripts nobody reads.
pilot-spec inverts that. Single-thread Claude. One SPEC.md. Math-glyph compression. §V invariants are the part the agent re-reads every turn, so task ten is built against the same constraints as task one. The human reviews the spec, not every diff — consistency holds without slowing the agent down.
Generation is cheap. The spec is what costs, and what's worth keeping. A token costs fractions of a cent; a tight §V invariant costs a real conversation. That's the half worth paying for — code gets rewritten, but §V invariants outlive the framework swap, and §B rows outlive the bug.
Why it works
One file, not a tree. SPEC.md is the whole spec — invariants, tasks, bugs — in a single file. Multi-file spec systems (e.g. GitHub Spec Kit) fan out across spec/, plan/, tasks/ — past a certain size, no agent run sees all of it, and the spec stops being a shared reference.
Deterministic re-grounding. Come back to the repo after a week, run /sdd:check — read-only drift report: what §V invariants the code violates, what §T tasks remain. Re-onboarding is one command, not transcript archaeology.
The drift report stays signal. /sdd:check is only as good as the spec is current. backprop fires automatically on every test/build failure — §B row plus, usually, a new §V invariant — so the spec stays honest, and the report stays trustworthy.
pilot-spec — spec-driven dev
One spec file. Five commands. Main-thread writes.
.md<br>/sdd:spec # write or amend the spec — invariants (§V), tasks (§T), bugs (§B)<br>/sdd:build # plan-then-execute next task; auto-backprops on test/build failure<br>/sdd:check # read-only drift report — code vs §V / §I / §T (--incremental for fast re-runs)<br>/sdd:explain # decompress any §X.n citation back into plain English">/sdd:design # propose-then-critique structural design → draft @ designs/.md<br>/sdd:spec # write or amend the spec — invariants (§V), tasks (§T), bugs (§B)<br>/sdd:build # plan-then-execute next task; auto-backprops on test/build failure<br>/sdd:check # read-only drift report — code vs §V / §I / §T (--incremental for fast re-runs)<br>/sdd:explain # decompress any §X.n citation back into plain English
SPEC.md is the only spec file. No docs/ tree, no JSON sidecars.
/sdd:spec is the only writer. /sdd:build may flip a task status cell (. → x); everything else routes through /sdd:spec.
Math-glyph compression. §V / §T / §B rows are ~30% denser than minimal prose and ~90% denser than the operator-facing prose a reviewer actually reads — bench, methodology, and worked examples in benchmarks/glyph/README.md.
Backprop reflex. Every test failure becomes a §B row plus, usually, a §V invariant the spec never forgets.
┌────────────┐ ┌────────────┐ ┌────────────┐ ┌────────────┐<br>│/sdd:design │──►│ /sdd:spec │──►│ /sdd:build │──►│ /sdd:check │<br>│...