Menu
SkillsMP has collected 22 skills from julienlegoux/skills. Open a skill to review its source and details.
Showing 22 of 22 collected skills.
Set up this machine for the lx skills — today the `external-reviewer` CLI the review skills hand their analysis pass to, by installing the binary, putting a provider credential in place through kern-link's `pi-ai login`, and assigning the light/standard/heavy…
Break one epic (docs/epics/epic-N-slug/EPIC_N.md) into PR-sized issues — one .md file each plus a real GitHub issue on the epic's milestone, linked as a native sub-issue of the epic's tracking issue. Use whenever the user wants an epic broken into tasks,…
Brownfield planning for one feature or serious change to an existing app — audit the code's blast radius, decide how the change lands through a user-triaged ledger under docs/planning/changes/, and deliver an EPIC_N.md (with GitHub milestone + tracking issue)…
Supervise the implementation of all remaining issues in an epic by delegating each one to an implement-issue subagent, watching CI, and merging green PRs into the integration branch until every issue is done. Use whenever the user wants an entire epic from…
Implement a single issue from docs/epics/ (produced by create-issues) as one focused, test-first PR — reconcile merged PRs, branch, strict red-green TDD against the acceptance criteria, open the PR, keep the bundle and GitHub issue in sync. Use whenever the…
Split a planning document (typically docs/planning/SCOPE.md) into one folder per epic under docs/epics/ — each with an EPIC_N.md, a GitHub milestone, and a tracking issue — ready for create-issues. Use whenever the user wants a plan or scope turned into…
Probe what the planning bundle depends on — tools, runtimes, services, accounts, secrets — before epics are cut, and write docs/planning/PREREQUISITES.md, which carries the gaps only the user can close and the register implement-epic gates on. Use when…
Semantic linter for OKF knowledge bundles — finds what a mechanical validator can't see (contradictions, index/log drift, duplicate concepts, taxonomy inconsistencies, stale content) and writes a severity-ranked report without modifying the bundle. Use…
Turn the findings accumulated across a repo's review reports — docs/reviews/*.md, plus legacy docs/REPORT_*.md — into one triaged remediation epic, docs/epics/epic-0-<slug>/EPIC_0.md with its milestone and tracking issue, that create-issues consumes…
Review split-epics output against the source plan — coverage, boundaries, ordering, OKF structure, GitHub state — and write a prioritized docs/reviews/<date>-epics-<subject>.md. Use when the user asks to audit, QA, or review created epics against the plan or…
Audit the code an epic actually shipped — review its merged diff against the epic's acceptance criteria, docs/planning/CONVENTIONS.md and the accepted drift, then record a disposition per finding in docs/reviews/<date>-implementation-<subject>.md for…
Review create-issues output against its epic (and the plan when useful) — coverage, sizing, ordering, OKF fields, GitHub linkage — and write a prioritized docs/reviews/<date>-issues-<subject>.md. Use when the user asks to audit, QA, or review generated issues.
First of the three planning skills (define-scope → define-specs → define-conventions) — decide what v1 ships into docs/planning/SCOPE.md through a decision ledger the user triages, taking CONCEPT.md as intake where define-concept produced one. Use when…
Third of the three planning skills (define-scope → define-specs → define-conventions) — instantiate the personal conventions baseline filtered by the stack in SPECS.md, decide only the deviations through a user-triaged ledger, and write…
Close out an epic after its implementation run stops — verify the epic's real state against GitHub and git, promote the drift its implementers recorded into docs/planning/DRIFT.md, close the milestone, and clean up the run's worktrees and merged branches. Use…
Shape a raw idea into a validated product concept through open discussion, recording only what the user validates into docs/planning/CONCEPT.md — the optional stage upstream of define-scope. Use when the idea itself is still forming and the user wants to…
Second of the three planning skills (define-scope → define-specs → define-conventions) — decide a project's one-way technical doors (stack, architecture, data model, auth, deployment) through a user-triaged decision ledger, writing docs/planning/SPECS.md. Use…
Reverse-engineer an existing codebase into the docs/planning/ bundle (SPECS.md + CONVENTIONS.md) by reading the code instead of interviewing the user — the brownfield entry point before define-change. Use to map, bootstrap, or refresh the planning bundle for…
Write and structurally validate documentation as Open Knowledge Format (OKF) bundles — markdown + YAML frontmatter with maintained index.md and log.md. Use whenever a session writes substantive markdown documentation (skip only incidental scratch files),…
Fold lessons from the current session back into the skill that caused them — diagnose from the conversation, propose a concrete edit, and after approval apply it to the skills repo and commit. Use whenever the user runs /improve-skill, says a skill…
Send feedback on the lx skills upstream as a GitHub issue on julienlegoux/skills — capture the user's own words verbatim, offer the technical context around them, redact anything private, and file it through gh or a prefilled browser URL. Use when a skill…
Add a new skill to this repo — prove the need actually repeats, place it against the skills that already exist, draft it to the repo's authoring contract, then validate, commit and reload. Use when the user wants a new skill, or wants a recurring prompt or…