All authors
Claude Skills by runlegion
github.com/runlegion15 skills0 installs5 views
- Legion DistillThe per-block gate for durable prose a stranger builds or acts from -- a spec, plan, intent, issue, or checkpoint -- and for the input you build one from. It does NOT govern an ephemeral team post, a status, or a signal note; those stay small -- a terse pointer, or better a directed signal to the one agent who needs it -- never carry-everything. The unit is the block: the writer distills each block as it writes it (one job, every word carrying, standing on the text alone, consistent with the ...Votes: 0GitHub stars: 3
- Legion MemoryAuto-triggered skill that reminds agents of the recall-before-grep doctrine. When an agent is about to search the codebase for answers, this skill reminds them to check legion memory first. Use this when the agent is researching a problem, looking for patterns, or trying to understand why something was built a certain way.Votes: 0GitHub stars: 3
- Legion Pr WriteCompose the PR body as a forcing function before opening a PR. Map each of the issue's acceptance criteria to the change that satisfies it -- in your own prose, with evidence -- and state what you deliberately did NOT do. Articulation is verification: writing the mapping makes you re-read your own diff as a reader and catch what you talked past while coding. Validate the body with `legion pr write-check`, which refuses an empty or boilerplate mapping and records the gate `legion pr create` re...Votes: 0GitHub stars: 3
- Legion ReviewThe review stage of the quality pipeline: simplify -> pr-write -> review -> verify. Fans out independent review dimensions over an open PR (spec-vs-diff, correctness, quality, security), adversarially verifies every HIGH/MED finding before reporting it, and records the result via `legion quality-gate record --skill legion-review` so downstream gates can require a clean review on HEAD. Run after `legion pr create`, before team sign-off and /legion:legion-verify.Votes: 0GitHub stars: 3
- Legion SimplifyReview the current branch diff for code quality issues: duplicate logic, unnecessary abstraction, stringly-typed state, and other structural problems. Articulate, per changed file, what you checked and why the verdict holds; `legion quality-gate check` validates the articulation (coverage + non-boilerplate + located evidence) and records the gate so `legion pr create` can verify clean state before opening a PR. Run this on every feature branch before a PR.Votes: 0GitHub stars: 3
- Legion VerifyThe final evidence gate before finished work is called done. Read the issue's acceptance criteria, the diff, and the test output, and emit one verdict per criterion -- pass, fail, or uncertain -- each with cited evidence (a test name, a file:line, an observable behavior). `legion verify --issue` records the verdict and decides the work's fate: all-pass records a clean gate, any fail hard-blocks, any uncertain (or a pass with no evidence) needs a human. For a solo engineering team this is the ...Votes: 0GitHub stars: 3
- Sd DiscoverThe evidence step of service design: take the research agenda's claims to test, listen to real discourse through eavesdrop, judge each claim against a same-lens control, ask the world what the corpus cannot settle, surface emergent insights the intent missed, and land one schema-valid Discovery document. Never cuts a claim: a contradicted or unevidenced claim is a finding the operator rules on. Parks on a missing corpus or an open question rather than guessing. Invoke after sd-intent-review.Votes: 0GitHub stars: 3
- Sd Ecosystem ImagineThe step where service design asks and answers every question about what turns the intent into a product -- who chooses it, who carries the risk, what it depends on, how value moves, what must be trusted, where it breaks -- and lands one schema-valid Ecosystem document with the answers built in. Five perspective passes find the questions; the step answers them from its own design reasoning and the Discovery, asks real people through eavesdrop what neither can settle, and brings the operator o...Votes: 0GitHub stars: 3
- Sd Intent ReviewThe first service-design step: read a repo's intent document and produce a research agenda -- candidate services to test and claims to test -- with every item tracing to an intent field. Outputs hypotheses to validate against real discourse, never designed services. Invoke at the start of a repo's service design, before any artifact exists.Votes: 0GitHub stars: 3
- Sd Service DesignRun a repo's service design through the first diamond -- discover the problem, then define the service: intent-review -> discover -> ecosystem-imagine -> the persona, journey, and blueprint writers. It ends at a defined service, not a solution, a spec, or code. This skill is the orchestrator, written as instructions -- the agent that invokes it conducts the pipeline by following it. Each step reads and writes documents in the legion store by id; a validation gate sits between steps; a step th...Votes: 0GitHub stars: 3
- Sd Write BlueprintWrite one service blueprint as a schema-valid legion document: the frontstage and backstage of a service across a sequence of steps, grounded in the journey it supports and the intent's real capabilities. Planned machinery is named as planned, never drawn as running. Invoke after the journey it backs exists.Votes: 0GitHub stars: 3
- Sd Write JourneyWrite one service-design journey as a schema-valid legion document: a persona through a scenario over time, with an emotional curve carried in plain emotion words drawn from evidence. Every low point traces to a Discovery insight; contradicted claims do not reappear as dips. Invoke after the persona it walks exists.Votes: 0GitHub stars: 3
- Sd Write PersonaWrite one service-design persona as a schema-valid legion document: behaviors, mental models, and the relationship to the service, every statement tracing to a Discovery insight or an intent field. Not demographics, not archetypes, no invented interiority. Invoke after the Discovery and ecosystem are landed.Votes: 0GitHub stars: 3
- Sd Write SpecWrite a scope's full requirement set -- FR and NFR documents -- from the intent/discovery layer, in one pass. The narrowing step of the engineering diamond, the third of legion's three: it crystallizes the IEEE 830-style requirement set the executor consumes, every SHALL naming what earned it and every gap escalated rather than resolved in-body. It is not part of the sd-service-design pipeline and has its own entry point. Two input modes: from an intent alone (system work) or from a landed se...Votes: 0GitHub stars: 3
- Legion Build To SpecThe orchestrator's gate at the pen. Run it before you send a brief to an implementer or a gate, create or edit an issue, record a finding disposition, or tell the operator what the spec requires. Every behavior claim in that text quotes the spec text it comes from; a mechanism the spec does not name never goes into a brief or an issue; acceptance text is frozen once a build starts. When reality and the spec disagree, you do not pick the answer -- you write a spec delta for the operator and bu...Votes: 0GitHub stars: 3