workflow
/workflow
Set up, update and align the engineering workflow. Installs the engineering loop and the upstream skills on a new machine, keeps them coherent as upstream changes, and aligns a project to the six conventions. Use when starting on a new machine or repo, when the user says set up / update / align / bootstrap the workflow, or when the engineering loop reports the repo or the toolchain is not ready.
- Author
- DawitLemmaBalcha ↗
- Repository
- agent-workflow ↗
- Licence
- MIT
- Last repository change
- 05.11.2026
Assessment and security
- Files in this package
- 4
- Scripts
- 1
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 05.11.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
- 1 scripts in this package. Review them before installing, as Claude may execute them.
Scripts: scripts/workflow.mjs
What it does and when to use it
Set up, update and align the engineering workflow. Installs the engineering loop and the upstream skills on a new machine, keeps them coherent as upstream changes, and aligns a project to the six conventions. Use when starting on a new machine or repo, when the user says set up / update / align / bootstrap the workflow, or when the engineering loop reports the repo or the toolchain is not ready.
Original author description
Set up, update and align the engineering workflow. Installs the engineering loop and the upstream skills on a new machine, keeps them coherent as upstream changes, and aligns a project to the six conventions. Use when starting on a new machine or repo, when the user says set up / update / align / bootstrap the workflow, or when the engineering loop reports the repo or the toolchain is not ready.
How it works
- Phase 1 — machine check
- Phase 2 — sync and install
- Phase 3 — project alignment
- Rules
SKILL.md preview
--- name: workflow description: "Set up, update and align the engineering workflow. Installs the engineering loop and the upstream skills on a new machine, keeps them coherent as upstream changes, and aligns a project to the six conventions. Use when starting on a new machine or repo, when the user says set up / update / align / bootstrap the workflow, or when the engineering loop reports the repo or the toolchain is not ready." --- # Workflow The one entry point. It answers three questions in order, and stops at the first one that fails: 1. **Is the toolchain installed and coherent?** (machine) 2. **Is it current with upstream?** (machine) 3. **Is this project aligned?** (repo) Never ask the user to run a script by hand. Run the commands yourself and report the outcome. Everything below runs from this skill's `scripts/` directory. ## Phase 1 — machine check ```bash node scripts/workflow.mjs status ``` Exit 0 means installed, pinned and coherent. Exit 3 means the toolchain is not installed yet (or `vendor/` is empty) — go to phase 2. Exit 1 means drift — go to phase 2 as well, but the sync will refuse to promote a bad set. If the repo path in `~/.dsh/workflow/config.json` no longer exists, say so and ask where the repo lives; the skill can still `doctor` a project but cannot install without the repo. ## Phase 2 — sync and install ```bash node scripts/workflow.mjs sync # fetch upstream, gate on coherence, promote or roll back node scripts/workflow.mjs install # install engineering-loop + the vendored set node scripts/workflow.mjs coherence # confirm the result ``` `sync` follows upstream `main` automatically. It is safe to run every time: it stages the new set beside the live one and **refuses to promote it if our skills would break** (a renamed skill we call, a skill flipped to user-invoked, a convention no longer mentioned upstream). On refusal it leaves the working set untouched and prints exactly what drifted — report that to the user and fix `skills/` before trying again. When it does promote, it prints the skills added or removed and the commits since the previous pin. If a commit looks like it touches skills, say so and summarise it before relying on the new behaviour. After installing, tell the user to restart the session (or wait for the catalog watcher) so the new skills load. `install` also writes `AGENTS.md` into the DSH home. That file is the global working agreement, not a project contract. ## Phase 3 — project alignment Check the project: ```bash node scripts/workflow.mjs doctor . ``` Then read `references/project.md` and apply only what is missing. The short version: - `AGENTS.md` (or `CLAUDE.md`) with a `## Workflow` block: `mode`, real `checks`, `high-risk` globs. Pointers to the rest of the docs, nothing more. - `GLOSSARY.md`: if the project keeps its language in `CONTEXT.md`, rename it and split out anything that is not language. - `docs/adr/` when there are decisions to record. - `CODING_STANDARDS.md` only when the repo already states rules to compile. - `docs/agents/` comes from `/setup-matt-pocock-skills`, run once by the human. - **Everything else stays where it is.** Architecture notes, runbooks, postmortems, plans: leave them, and point at them from `AGENTS.md`. No renaming, no archive, no second home. Report what you created and what you deliberately left alone. ## Rules - **Never edit `vendor/`.** It is upstream's code, replaced on every sync. - **Never edit upstream's skill bodies to fit the project.** Local variance goes in the repo's `AGENTS.md`, `CODING_STANDARDS.md` or `docs/agents/`. - **Do not silently rewrite `skills/` to satisfy a check.** Drift is a signal to the human, not a licence to rewrite our prompts. Propose the change; if it is real work, run the engineering loop on it. - **Do not create folders the conventions do not ask for** to make the doctor pass. Missing optional docs are advisories, on purpose. - `--dry-run` exists on the installer; prefer it before the first install on a machine that already has skills.
Files in this package (4)
- SKILL.md 4 KB
- references/machine.md 3 KB
- references/project.md 3 KB
- scripts/workflow.mjs 20 KB
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · DawitLemmaBalcha/agent-workflow | 100 | MIT |
| jeremylongshore/tons-of-skills-marketplace | 100 | MIT |
| SimHacker/moollm | 100 | MIT |
| mlophez/polix-ai | 100 | Apache-2.0 |
| stellarie/minimal-agent-kit | 100 | MIT |
| waynesutton/builder-skills | 100 | Apache-2.0 |
| claude-world/director-mode-lite | 100 | MIT |
| zhinkgit/embeddedskills | 100 | MIT |
| anthillapp/anthill | 100 | MIT |
Database snapshot: 13.11.2026 · package version a866cc30cbb5 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 96repo-bootstrap
Use when the user asks to bootstrap a new repo or project. - 100project-create
Initialize a new project with full setup — repo structure, docs, quality tools, and CI/CD. Use when starting a brand-new project from scratch. Trigger on "create a new project", "initialize a project", "set up a new repo", "bootstrap a project". - 100bootstrap
Use this skill when the user asks to bootstrap, set up, or initialize the App Project Workflow (router skill, worker, tester, reviewer, Explore subagents, ticket board, worktree guard tools) in a new or empty project folder. Interviews the owner about the project, writes a first… - 100setup
One-time machine setup to work in a team GitHub repo - install git and gh, log in to GitHub, set git name/email, get access to and clone the repo. Use when someone says "set me up", "first time", "how do I get the repo", or git/gh isn't installed or authenticated. - 100upstream-contrib
Explicit-use only — invoke when the user explicitly names this skill, or when an active explicitly invoked workflow calls it. Runs the explicitly requested workflow for contributing consumer changes upstream to fx/ui. - 100update
Update NanoClawbster from upstream. Fetches latest changes, merges with your customizations and skills, runs migrations. Triggers on \"update\", \"pull upstream\", \"sync with upstream\", \"get latest changes\".