work

Solid

Entry point for any task in this repo — "let's do X", "pick up B123", "fix", "add", "change". Checks the ask is still true and unclaimed, sizes it S/M/L, picks the lightest safe path (direct edit, /plan, /research) and says who does what on which model. Use before touching code; skip only for a one-line answer.

AI & Automation 63 stars 0 forks Updated today Apache-2.0

Install

View on GitHub

Quality Score: 87/100

Stars 20%

Recency 20%

100

Frontmatter 20%

Documentation 15%

100

Issue Health 10%

License 10%

100

Description 5%

100

Skill Content

Task: $ARGUMENTS ## 1. Is it still true, and does anyone hold it? - If it names a `B` id: the line exists in `BACKLOG.md` (a deleted line means it shipped — check `CHANGELOG.md` and `FEATURES.md` and stop cleanly). - `git log --oneline -15 -- <paths it touches>` and `gh pr list --search "<keywords>"`: work that already landed or is open in a PR is continued, not duplicated. A GitHub issue is claimed before work starts (`gh issue edit <n> --add-assignee @me`) and released if the work parks. - `docs/work/`: an open work file on this topic means resume it from its **Handoff** section. - The premise: read the code the ask describes. If the described behaviour is not what the code does, say so before planning anything. ## 2. Size it | Size | Shape | Path | |---|---|---| | S | one file, no schema/protocol/surface change, verification obvious | do it here, then `/gate` and `/ship` | | M | 2–5 files, a test change, maybe a doc | `/plan` with one track per file group, then `/build` | | L | new capability, new source, new metric, migration, protocol, a number a reader sees | `/plan` with alternatives and a challenger; `/research` first if the roadmap does not already justify it | Anything that changes a stored field or a migration is L regardless of line count (`.claude/rules/store.md`). Anything that changes a figure a reader sees is at least M and ends with `corpus-prover`. ## 3. Who does what Write the table before starting; delegate only what the table says. | Work ...

Details

Author: assaio
Repository: assaio/assaio
Created: 2 months ago
Last Updated: today
Language: Go
License: Apache-2.0

Integrates with

SQLite · Database

Similar Skills

Semantically similar based on skill content — not just same category

Code & Development Featured

auto

Autonomous, non-interactive run of the whole chain — work → plan → build → gate → review → ship up to the PR — for a task or B-id, without questions. Takes the most reversible decision when unsure and records it in the work file as "decided alone … reverse by …". Stops only at hard lines (merge, tag, push to main, money, protected contracts). Exits cleanly when nothing is left to do.

63 Updated today

assaio

Data & Documents Listed

plan

Before non-trivial work - read the code, ask only the questions whose answers change the work, one at a time, then write a half-page plan with the smallest version, what breaks at 3am, rollback, and the commands that will prove it done. Saves the plan to a file and waits for a go. User-invoked with /silicon-valley:plan.

0 Updated 2 days ago

harshitt13

Code & Development Solid

plan

Writes the ONE work file for a task — docs/work/<date>-<slug>.md holding spec, plan, journal and handoff together — with tracks a coder can take unread. Use for M and L work, "plan this", "write the spec", "how would we build". For L work it adds alternatives and a challenger review before any code exists.

63 Updated today

assaio