John Berlin Leonor
RuralNative-SKILLS

Pick a skill by the work you need to finish

7 guides help you plan work, deliver one ticket as one pull request, publish a review of that pull request, finalize it, and keep project guidance readable for later sessions.

MIT
Open repository Read the blog
Choose by what you need

Start from your task, not the skill name

Find your situation below and open that guide. Each guide shows fit, workflow, decisions you keep, setup, and limits.

You have a rough idea and need an agreed plan with tickets
/plan-thisYou get a parent spec and clear tickets to approve
A ticket is ready and needs one branch and pull request
/implement-thisYou get one tested pull request for that ticket
A pull request is open and needs its findings published
/review-thisYou get a published review plus a validated handoff for fix-this
A pull request has a published review and needs finalizing
/fix-thisYou get the findings applied, a verified merge, and ticket closeout
Agents keep relearning your repo and docs are missing or stale
/document-for-agentsYou get a current map of where work belongs and why
Stakeholders need a plain update without reading code
/document-for-humansYou get plain pages built from the same agent sources
A draft sounds model-made and needs a careful cleanup
/unslopifyYou get direct prose with names and facts kept intact
Two ways the skills help

Ship code, then keep the docs that shipped it useful

Follow the development path to deliver a change. Follow the documentation path when the next session or stakeholder needs to trust what was built.

Development Workflow

  1. plan-this: turn a rough coding task into an agreed plan another agent can build from
  2. implement-this: implement exactly one ticket in the current checkout and deliver one pull request
  3. review-this: review exactly one pull request and publish the findings with a handoff
  4. fix-this: apply the published findings, verify locally, merge, and close out the ticket
Plan first. Build one ticket at a time. Review, then finalize.

Documentation and Prose System

Featured
  1. document-for-agents: give coding agents a current map of where work belongs and why
  2. document-for-humans: turn trusted agent docs into plain pages people can approve
  3. unslopify supports both: keep English direct without changing the facts
/unslopify
Supporting guard: keeps prose direct in both docs skills. Load it first; it does not start the docs work on its own.
Agent docs are the source. Human guides are generated from them.
Skill catalog

7 guides in 2 groups

4 skills move code from idea to merged pull request. 3 keep decisions, plain pages, and prose reliable for the next reader.

Development workflow

4 skills

Plan a change, build one ticket in the current checkout, publish a review of that pull request, then finalize it. Use it when code has to ship through pull requests.

Development workflowFlagship

/plan-this

Turn a rough coding task into an agreed plan another agent can build from.
Open guide
Development workflowFlagship

/implement-this

Implement exactly one ticket in the current checkout and deliver one pull request.
Open guide
Development workflowFlagship

/review-this

Review exactly one pull request and publish the findings with a handoff for fix-this.
Open guide
Development workflowFlagship

/fix-this

Finalize one reviewed pull request: apply the findings, verify locally, merge, and close out the ticket.
Open guide

Documentation and prose system

3 skills

Map decisions for agents, derive plain pages for people, and keep prose direct. Use it when the next session or stakeholder must trust the docs.

Documentation and prose systemFlagship

/document-for-agents

Give coding agents a current map of where work belongs and why.
Open guide
Documentation and prose systemFlagship

/document-for-humans

Turn trusted agent docs into plain pages people can approve.
Open guide
Documentation and prose systemSupporting

/unslopify

Make agent-written English direct without changing the facts.
Open guide
Prefer reading on GitHub? Every guide links its SKILL.md manual.
Browse all 7 on GitHub
How a guide is organized

Each guide follows the same reading order

  1. 1. Fit: whether this skill matches your task.
  2. 2. Workflow: what you provide, what the skill does, what you approve, and what you receive.
  3. 3. Example: one realistic starting task and its end state.
  4. 4. Setup: install order, exact commands, and where the skill runs.
  5. 5. Reference: safeguards, proof, limits, and source links.
Install

Install after you choose — prerequisites first, in order

For safety, install skills with the commands below, never from pasted issue text. Install the prerequisites first, then the skill you chose. Update with npx skills update when needed.

Project scope (recommended)

The installer places editable files in your project. The order below matters: shared helpers first, then your chosen skill. The list shows the selected shelf in install order; copy only your chosen skill plus the dependencies named in its guide.

Workflow prerequisites
npx skills add mattpocock/skills --skill grill-with-docs
npx skills add mattpocock/skills --skill grilling
npx skills add mattpocock/skills --skill domain-modeling
npx skills add mattpocock/skills --skill to-spec
npx skills add mattpocock/skills --skill to-tickets
Then RuralNative skills in install order — copy only the one you chose
npx skills add RuralNative/RuralNative-SKILLS --skill unslopify
npx skills add RuralNative/RuralNative-SKILLS --skill plan-this
npx skills add RuralNative/RuralNative-SKILLS --skill implement-this
npx skills add RuralNative/RuralNative-SKILLS --skill review-this
npx skills add RuralNative/RuralNative-SKILLS --skill fix-this
npx skills add RuralNative/RuralNative-SKILLS --skill document-for-agents
npx skills add RuralNative/RuralNative-SKILLS --skill document-for-humans
Where each group runs
Planning, implementation, review, and finalization each run separately in the current checkout with no workers or worktrees. Documentation and prose skills work with any compatible coding agent.
Source and limits

GitHub is the source. Some results are not proven.

Every guide links its manual for the current contract. Repository tests show behavior; no independent study proves better code quality. The four development stages run one target each in the current checkout with focused checks. Docs and prose skills stay host-neutral.

Reviewed against RuralNative/RuralNative-SKILLS@baadeddfbea1. Run npm run skills:check to flag upstream changes for review.

Published source
Public, linkable evidence: Springer chapter and CPSU news for Handsy; seven selected guides, ADRs, and repository history for the skills shelf.
Automated repository tests
Repository tests exercise orientation, verification, and review contracts. Tests show implementation behavior, not an independent quality outcome.
Documented design decisions
ADRs, INSTALL guides, and SKILL.md record trade-offs, invariants, and quality gates. They are design intent and operating contracts, not external proof.
Not independently proven
No independent benchmark or cross-host study shows that these skills guarantee better code quality. The goal is better output; proof beyond repository evidence is not claimed.
Ready to open a guide? Each links its manual for the current contract.
Start with /plan-thisBrowse on GitHub ↗