orchestrate
wellgent/skills · skills.sh
Open source Repository Open in the app JSON README (API)
About
Skill publicada por wellgent/skills no skills.sh. Instale com: npx skills add wellgent/skills@orchestrate
Details
- Kind
- Agent skills
- Publisher
- wellgent
- Origin
- skillssh
- Category
- ferramentas
- Last push
- 2026-10-06T08:46:31Z
- Repository state
- ativo
- Language
- Shell
- License
- MIT
- Added
- 2026-10-07 06:31:25
- Updated
- 2026-10-07 06:31:25
- Origin id
wellgent/skills/orchestrate
README
# Wellgent Agent Skills The agentic engineering approach we design and run in production at [Wellgent](https://wellgent.ai), published for anyone to adopt: the development flow, the setup paths, and the normative doctrine behind them. ## The flow [`FLOW.md`](https://github.com/wellgent/skills/blob/HEAD/FLOW.md) is the development flow on one page: eleven stages from Readiness to Retro, each with one role, one input, one output and a quality bar, and the artifacts handed between them. [`GLOSSARY.md`](https://github.com/wellgent/skills/blob/HEAD/GLOSSARY.md) defines its terms. The flow is read in place from one checkout of this repo per run host, at `~/repos/wellgent-skills`. Nothing from it is installed or pinned into a project, so a flow change reaches every project with one `git pull` on the host. A project pins only the third-party skills a step names, by commit sha. ## Layout - [`FLOW.md`](https://github.com/wellgent/skills/blob/HEAD/FLOW.md), [`GLOSSARY.md`](https://github.com/wellgent/skills/blob/HEAD/GLOSSARY.md) - the flow doc and its language. - `lead/` - the lead skill: the stages the lead runs itself (Readiness, Shape, Plan, Release, Retro) and how it starts and sequences every step. Linked into the user's skills directory on each run host. - `stages/<stage>/` - one skill per spawned stage: `ux-design`, `system-design`, `grooming`, `build`, `review`, `qa`, `audit`. Each opens with its header from `FLOW.md`. `flow spawn` puts the skill's absolute path in the session's start prompt; a `-second` step and the `audit-architecture` steps read their stage's skill. - [`bin/`](https://github.com/wellgent/skills/blob/HEAD/bin/) - the `flow` command (`spawn`, `gate`, `land`, `tick`, `report`, `ask`, `ledger`, `sources`, `ready`, `trust`) and its scripts, Bash with `jq`; `flow help` lists them and [`bin/README.md`](https://github.com/wellgent/skills/blob/HEAD/bin/README.md) holds what they read. `bin/flow` is linked into the user's `PATH` on each run host. - `ledger/` - the ledger schema and the price table the cost script reads. The ledger files themselves live in the driving brain. - [`templates/artifacts/`](https://github.com/wellgent/skills/blob/HEAD/templates/artifacts/) - the hand-off artifact formats `FLOW.md` names. - [`templates/project/`](https://github.com/wellgent/skills/blob/HEAD/templates/project/) - what the setup skills scaffold into a project: `AGENTS.md`, `docs/agents/dev-loop.md`, `CODING_STANDARDS.md` and the bug issue template with its origin-spec field. - [`templates/brain/`](https://github.com/wellgent/skills/blob/HEAD/templates/brain/) - what the setup skills scaffold into a driving brain: the flow config and the project card. - [`source-log.md`](https://github.com/wellgent/skills/blob/HEAD/source-log.md) - every upstream source the flow depends on, with the last version seen, its date and, for a source of pinned skills, the commit every brain and project pins. Readiness reviews it in full. - [`setup/`](https://github.com/wellgent/skills/blob/HEAD/setup/) - the setup skills. - [`standards/`](https://github.com/wellgent/skills/blob/HEAD/standards/) - the doctrine. ## Setup paths Operator skills under [`setup/`](https://github.com/wellgent/skills/blob/HEAD/setup/): run from a checkout of this repo against a target path, in either harness (`.claude/skills/` and `.agents/skills/` link to them). - **setup-brain** - scaffold the flow into a driving brain: flow config, labels, the lead's pinned skills, and a card, config entry and ledger directory per project. - **setup-project** - bring a project onto the flow: folder trust, pinned skills, the three project docs from the templates, critical journeys, tracker labels. It names no stack. - **setup-web-stack** - the stack setup for a web product: a curated [catalog](https://github.com/wellgent/skills/blob/HEAD/setup/setup-web-stack/catalog.md) of community skills, quality tooling and known-good configs, the journey tests and the Convex branch. - **setup-web-product** - the golden path for a new web product, each stage deferred to its installer. The first two are idempotent and Readiness re-runs them; [`setup/requires.json`](https://github.com/wellgent/skills/blob/HEAD/setup/requires.json) holds what a brain and a project must carry, and `flow ready` checks it. ## The doctrine [`standards/web-products.md`](https://github.com/wellgent/skills/blob/HEAD/standards/web-products.md) is the normative approach the setup skills implement: judging criterion, frontend and toolchain stances, hosting classes, data layer, quality gate, skills model, and methodology. It carries the slow-moving rules and every stack-specific one; the flow skills name no stack. Exact version pins and per-project membership are operational state and live in the adopter's own private registry. ## What belongs here Everything we use regularly lives here - shared with the world, friends, clients, and the machines we manage. Truly internal things live at project or repo level: one project's specifics stay in that project; project cards, iteration maps, ledgers, version pins and fleet machinery stay in private repos. Everything published here is internals-free: no person, project, company or host is named, and it works unmodified from a stranger's checkout. ## Conventions the flow assumes - [mattpocock/skills](https://github.com/mattpocock/skills) pinned in the project: the flow runs its `to-spec`, `to-tickets`, `implement-spec`, `code-review` and `retro` as written and builds only what they lack. - A GitHub-style issue tracker with sub-issues and native blocking edges. - herdr on the run host: every step runs as its own session and reports to the lead's session. - Claude Code and Codex on the run host: a step's harness follows its model in the flow config. ## License [MIT](https://github.com/wellgent/skills/blob/HEAD/LICENSE)