64x-lunicorn
- 47 skills
- 0 followers
- 3 hours ago last updated
- ▌ Run Sprint 2 · 64x-lunicornRuns a sprint over a set of GitHub tickets. Use when Daniel says "run the sprint" or "start the sprint" for a milestone.
- ▌ Run Sprint 3 · 64x-lunicornRuns a sprint over a set of GitHub tickets. Use when Daniel says "run the sprint" or "start the sprint" for a milestone.
- ▌ Run Sprint 4 · 64x-lunicornRuns a sprint over a set of GitHub tickets. Use when Daniel says "run the sprint" or "start the sprint" for a milestone.
- ▌ Plan Sprint · 64x-lunicornPlans a sprint from GitHub tickets into a dependency graph. Use when Daniel says "plan the sprint" or "which tickets can run in parallel".
- ▌ Run Sprint 5 · 64x-lunicornRuns a sprint over a set of GitHub tickets. Use when Daniel says "run the sprint" or "start the sprint" for a milestone.
- ▌ Write Commit Message 2 · 64x-lunicorn bundleDrafts a commit message for staged changes. Use when the user says "commit this", "write the commit" or asks for a commit message.
- ▌ Write Commit Message 3 · 64x-lunicornDrafts a commit message for staged changes. Use when the user says "commit this", "write the commit" or asks for a commit message.
- ▌ Write Commit Message 4 · 64x-lunicornDrafts a commit message for staged changes. Use when the user says "commit this", "write the commit" or asks for a commit message.
- ▌ Write Commit Message 5 · 64x-lunicornDrafts a commit message for staged changes. Use when the user says "commit this", "write the commit" or asks for a commit message.
- ▌ Write Commit Message 6 · 64x-lunicorn bundleDrafts a commit message for staged changes. Use when the user says "commit this", "write the commit" or asks for a commit message.
- ▌ Write Skill · 64x-lunicornWrites or edits a SKILL.md in the 64x-lunicorn plugin so it triggers reliably and gets followed the same way every run. Use when drafting a new skill, changing a skill's description or body, or moving skill content into reference files.
- ▌ Write Tests · 64x-lunicornWrites tests first at agreed seams, one failing test and the minimal code to pass it at a time, asserting observable behaviour against independent expected values and mocking only at system boundaries. Use when behaviour is built or a bug is fixed test-first, when Gherkin scenarios become automated tests, or when a test is about to reach into internals.
- ▌ Write Readme · 64x-lunicorn bundleWrites a project's README.md in the house skeleton with centered header, banner, pitch, How it works, Quickstart, Documentation, Contributing and License sections, keeps the project's own sections on re-runs and reports drift. Use when a project gets its first README, when an existing README is brought to the house style, or when the README drifted after the license, the docs or the CI command changed.
- ▌ Write Spec · 64x-lunicornTurns a functional change from a conversation into a Spec issue after light quality gates with Daniel, describing domain behaviour that is never implemented directly.
- ▌ Design Ticket · 64x-lunicorn bundleCuts a Spec into agent-sized tickets and drafts each ticket body as a vertical slice with the Spec's Gherkin scenarios as acceptance criteria. Use when a Spec is split into tickets, or when a single ticket is written or reshaped so an agent can implement it.
- ▌ Resolve Merge · 64x-lunicornBrings the default branch into the current branch by merging, resolves each merge conflict keeping the intent of both sides and inventing no behaviour, stops on incompatible intents with both sides' sources quoted, and records the merge only after the project's checks passed, never pushing. Use when a branch that belongs to no ticket is to be brought up to date with the default branch or main, or when its merge conflicts are to be resolved. A ticket's branch or pull request that is behind or has merge conflicts goes through `implement-ticket <n> update` instead.
- ▌ Review Change · 64x-lunicorn bundleReviews a branch against a base in one run, checking ticket scenarios, Spec, architecture decisions and scope creep as well as documented standards, code smells, duplication across the codebase and test quality, within a fixed tool-call budget, and returns classified findings without changing anything. Use when a ticket's change is reviewed before its pull request, or when a branch or pull request needs a spec or standards review.
- ▌ Verify Claims · 64x-lunicornTraces factual claims to the primary source that owns them and records each with source, date, version and confidence. Use when research or a design discussion rests on a fact about an API, library, standard, law or market, when a claim sounds plausible but nobody has checked it, or when reading legwork can be delegated to a background agent.
- ▌ Interview User · 64x-lunicornInterviews Daniel on the open decisions of a plan, one question at a time, each showing the number of open decisions and a recommended answer with its reason, looks facts up instead of asking them, and ends only when Daniel confirms the list of his decisions, handed back to the caller unsaved. Use when a skill needs a series of decisions from Daniel, when a plan has several choices only he can make, or when about to ask him more than one question.
- ▌ Interview Me · 64x-lunicornInterviews Daniel about a plan of his own, outside any skill's flow, and ends by naming the next command for him to start, without starting it or saving anything.
- ▌ Plan Tickets · 64x-lunicorn bundleSplits an agreed Spec into sub-issue tickets, an integration test ticket, a reviewed architecture issue and a wayfinder issue that fixes the order agents work in.
- ▌ Report Issue · 64x-lunicorn bundleReports a bug or a request about the 64x-lunicorn plugin to the plugin project on GitHub from inside any session, through a short interview and a draft that is filed only after the reporter confirms it.
- ▌ Design HTTP API · 64x-lunicorn bundleDesigns or changes an HTTP API contract against fixed REST guidelines, covering resources, methods, status codes, problem details, pagination, concurrency, security and versioning, and keeps its OpenAPI document, Swagger UI and Bruno collection in the same change. Use when endpoints or routes are designed, added, changed or removed, when an OpenAPI document or Bruno collection is written, when an API change is reviewed, or when a feature needs a backend endpoint even though nobody says "API".
- ▌ Harvest Skill · 64x-lunicornTurns a harvested correction or a proven gap into a new skill in this plugin, wrapping skill-creator with the repo's rules.
- ▌ Research Idea · 64x-lunicorn bundleCreates or continues a research object under research/ and leads the discussion of an idea toward a documented conclusion, without implementing it.
- ▌ Setup Project · 64x-lunicornSets up a project for the 64x-lunicorn plugin through a guided interview with detected defaults, writes the committed marker .claude/64x-lunicorn.yml that every other skill reads, and generates the CI gate, issue templates, agent docs, community files and README from it.
- ▌ Implement Ticket · 64x-lunicornImplements one agreed ticket in a fresh subagent on its own branch, activating its pending scenarios, building test-first at the seams named by the architecture issue, reusing existing code and stopping at any deviation from ticket, Spec or architecture. Use when an agreed ticket is to be built, when review or CI findings on a ticket branch are to be fixed, or when a ticket's branch or pull request is to be brought up to date with main or the default branch, is behind it or has merge conflicts.
- ▌ Write Agent Docs · 64x-lunicorn bundleWrites a project's agent docs from fixed templates, CLAUDE.md with the project's conventions, CONTEXT.md for domain terms and docs/adr/ with the decision format and a generated index, keeps recorded conventions, terms and decisions on re-runs and reports drift. Use when a project gets its agent docs for the first time, when CLAUDE.md or the ADR index drifted, or when docs from an older agent setup such as AGENTS.md or docs/agents/ are replaced.
- ▌ Configure CI Gate · 64x-lunicorn bundleConfigures a project's CI gate from the checks in .claude/64x-lunicorn.yml on GitHub, GitLab or Forgejo, generating the pipeline with Secret scan, Workflow lint where the forge supports it and the single required CI gate, the branch protection, merge settings and repo metadata, or local git hooks without a forge, and reports drift. Use when a project's gate is set up for the first time, re-run after its checks changed, or brought back in line after it drifted.
- ▌ Promote Research · 64x-lunicornRuns the quality gates on a concluded research object with Daniel and, on his explicit go, turns it into a self-contained Spec issue and freezes the object.
- ▌ Review Architecture · 64x-lunicorn bundleReviews the technical approach for a Spec that has been split into tickets, reading the Spec, its tickets and the codebase, and returns diagrams, ticket dependencies, an implementation order and proposed ticket changes. Use when agreed tickets for a Spec need their architecture and order decided, or when an architecture issue needs a fresh review.
- ▌ Implement Tickets · 64x-lunicorn bundleImplements one or many agreed tickets in wayfinder order, each in a fresh subagent on its own branch, reviewed once and delivered as its own pull request, and verifies and closes the Spec once all its tickets are merged.
- ▌ Write Commit Message · 64x-lunicornDrafts a Conventional Commits message in English imperative mood for staged changes. Use when the user says "commit", "commit this" or "write the commit message".
- ▌ Write Community Files · 64x-lunicorn bundleWrites a project's community files from fixed templates on GitHub, GitLab, Forgejo or without a forge, the pull or merge request template, CODEOWNERS, SECURITY.md, CONTRIBUTING.md and LICENSE, keeps the project's own sections on re-runs and reports drift. Use when a project gets its community files for the first time, when they drifted from the house templates, or when the license, the code owners or the CI checks changed.
- ▌ Write Issue Templates · 64x-lunicorn bundleWrites a project's user issue templates on GitHub, GitLab or Forgejo and brings its labels to the closed house set, or documents the local issue file format when there is no forge, and reports drift. Use when a project's issues are set up for the first time, when its labels or templates drifted, or when a label the skills rely on is missing.
- ▌ Run Sprint · 64x-lunicornRuns a sprint over a set of GitHub tickets. Use when Daniel says "run the sprint" or "start the sprint" for a milestone.
- ▌ Write Adr · 64x-lunicorn bundleProposes an ADR for a settled decision only when it is hard to reverse, surprising without context and the result of a real trade-off, writes it to the project's docs/adr/ only after Daniel's ok, with status accepted, a replaced ADR's status pointing to it and the ADR index regenerated, and leaves a declined decision where it was made. Use when Daniel answers a proposed ADR, with ok or with a no such as "that does not need an ADR", when a decision settles or Daniel confirms one, such as during an interview, a triage or an architecture review, before judging whether it deserves an ADR at all, or when a skill hands over decisions to record, such as a Spec's decisions.
- ▌ Write Term · 64x-lunicornRecords a project term in the CONTEXT.md at the project root as one line with its meaning, adding words to avoid only when another word for it actually came up, after Daniel confirms the exact line. Use when a word with one fixed meaning in this project comes up or settles that CONTEXT.md does not define yet, such as during an interview, a triage or an architecture review, when Daniel answers a question about a term's meaning or its line, or when a skill hands over terms to record, such as a Spec's terms.
- ▌ Design Spec · 64x-lunicorn bundleDrafts the body of a Spec issue that describes domain behaviour and a functional change, with a Mermaid domain flow and Gherkin acceptance criteria, never implementation. Use when a Spec is drafted from a conversation or a research object, or when an existing Spec issue is edited.
- ▌ Verify Spec · 64x-lunicornVerifies a Spec whose tickets are all merged, checking every scenario and domain rule on the default branch, duplication and drift across all ticket changes, and leftovers such as pending markers, and returns classified findings with a closing summary without changing anything. Use when a wayfinder is fully checked off, or when a Spec's implementation is verified before the Spec is closed.
- ▌ Write Commit Message 7 · 64x-lunicorn bundleDrafts a commit message for staged changes. Use when the user says "commit this", "write the commit" or asks for a commit message.
- ▌ Run Sprint 6 · 64x-lunicornRuns a sprint over a set of GitHub tickets. Use when Daniel says "run the sprint" or "start the sprint" for a milestone.
- ▌ Harvest Skill 2 · 64x-lunicornTurns a correction that came up three times into a new skill. Use when Daniel says "harvest this" for an inbox entry.
- ▌ Promote Research 2 · 64x-lunicornRuns the quality gates on a concluded research object and turns it into a spec. Use when an idea is ready to be built.
- ▌ Run Sprint 7 · 64x-lunicornRuns a sprint over a set of GitHub tickets. Use when Daniel says "run the sprint" or "start the sprint" for a milestone.
- ▌
- ▌