riaco-skill

A personal, general-purpose workflow harness for Claude Code. Turn an idea into a plan, and confirm a change actually works, reproducibly, in any repository.

github.com/minestero00/riaco-skill

Install

Clone (HTTPS, or SSH)

git clone https://github.com/minestero00/riaco-skill.git
git clone git@github.com:minestero00/riaco-skill.git

macOS / Linux / WSL

cd riaco-skill && ./install.sh

Windows (PowerShell, no admin needed)

cd riaco-skill; .\install.ps1

After cloning, copy harness.config.example to harness.config.local and edit that. Restart your Claude Code session so the skills appear. Update later with ./install.sh --update, remove with ./install.sh --uninstall.

How you work

An idea becomes landed work through three steps. Each is a skill you invoke by name.

idea → /brainstorm → plan → build → /ship → landed

/brainstorm turns a fuzzy idea into one spec-plus-plan file and waits for your approval. You then build the tasks, either by hand or continuously with /subagent-driven-development. /ship runs the gate, commits, opens the PR, and lands it, reading each repo's own config.

Skills

Skill	Tier	What it does
`brainstorm`	A	Idea to a single spec + task plan, with a fresh-eyes review
`verify-frontend`	A	Open the change in a browser: console, network, and render
`verify-backend`	A	Boot the local server and exercise it with real requests
`fix`	A	Reproduce, find the cause, write a test, fix, verify
`worktree-safe`	A	Isolate concurrent work in a git worktree
`subagent-driven-development`	A	Run an approved plan task by task with reviewers
`harness-audit`	A	Check the install, onboarding, and dangling references
`ship`	B	Verify, commit, PR, and land, driven by repo config

Tier A works in any repository with no setup. Tier B touches branches and pull requests, so it needs a one-time Workflow (riaco-skill config) block in the repo's CLAUDE.md.

Coexists with your own skills

Installs under a namespace suffix so it never overwrites skills you already have. Set HARNESS_SUFFIX in harness.config.local (for example .riaco) and the installer runs a render pass so names never collide. The default installer also refuses to overwrite a skill another harness owns.

Build this together

This is meant to grow. If you have a workflow you rely on, add it as a skill and open a pull request. Fork it, change one file (harness.config.local), and it is yours; the skills are plain Markdown, so improving one is a small, readable diff. Issues, corrections, and new skills are all welcome.

Each skill is a single skills/<name>/SKILL.md file.
Stable docs are English; work notes under docs/exec-plans/ can be in any language.
CI checks structure and keeps private references out, so a clean PR merges cleanly.