Top AI Repos — open-source AI, indexed and scored
Top AI Repos tracks AI repositories on GitHub and answers two different questions about each one: is it moving right now, and would you bet a product on it.
Top AI Repos tracks AI repositories on GitHub and answers two different questions about each one: is it moving right now, and would you bet a product on it.
Agentic Development skills behind the JS Mastery workflow
| Date | Stars |
|---|---|
| 2026-07-31 | 744 |
| 2026-08-05 | 770 |
| 2026-08-06 | 770 |
Today
— stars today
This week
— stars this week
This month
— stars this month
Momentum
0.0
growth rate 0.00%/day
# Engineering Workflow Skills A set of [Agent Skills](https://agentskills.io) that take a change from a vague idea to shipped, verified, documented code, for any AI coding agent. One skill per phase. Run only the ones a change needs, in any order. The state lives in files (a scope, specs, AGENTS.md, tests), not in a chat session. So work survives across sessions, picks up where it left off, and works for a whole team. ``` idea → /scope → /audit → /architect → /develop → /check verify → /test → /check review → /document → /sync ``` Run `/debug` anytime something breaks. Run a bare `/scope` anytime to see where things stand. > 📖 **Want the full picture?** Read the **[Workflow Guide](docs/workflow-guide.md)** — a plain-language walkthrough of every skill, the files that carry the work, who owns what, and one idea followed all the way from scope to shipped. ## The skills | Skill | What it does | |---|---| | `scope` | Turns a product idea into a living, coarse scope and keeps it current as you ship. | | `audit` | Writes the AGENTS.md context files every other skill reads. | | `architect` | Makes a load bearing decision and writes it as a build spec in `docs/specs/`. | | `develop` | Builds a feature, UI or backend, from its spec. Gates to `/architect` if a decision is owed. | | `check` | Confirms a change before merge. `/check verify` runs the real app; `/check review` reads the code on a second model. | | `test` | Writes a test suite for the code you just changed. | | `document` | Writes the PR text, changelog, release note, or postmortem from the real diff. | | `sync` | Keeps AGENTS.md, the scope, and spec statuses current after a change. | | `debug` | Finds and fixes the root cause of a bug, then hands a regression test to `/test`. | Hardening (systems level failure mode analysis) is temporarily removed and will return as a system design specialization. ## Install Uses [npx skills](https://github.com/vercel-labs/skills). Pick your agent: ```bash # Claude Code (installs into .claude/skills, then restart Claude Code) npx skills@latest add jsmastery-pro/skills -a claude-code # Generic .agents/skills, read by Codex and other agents npx skills@latest add jsmastery-pro/skills ``` Works on any Agent Skills client (Claude Code, Cursor, Codex, Gemini CLI, and [more](https://agentskills.io/clients)). Commit the installed skills folder to share the workflow with your team. Each skill's instructions live in its `SKILL.md`, which is what every client reads. The `agents/openai.yaml` beside it is interface metadata only (the name, blurb, and opening prompt Codex shows in its agent picker); it carries no logic of its own. ## Where to start **New product (greenfield):** `/scope` the idea, then `/architect` the stack, then scaffold the project, then `/audit` to seed AGENTS.md from the real project, then the feature loop. The stack is decided and the project scaffolded before `/audit` runs, so it reads a real project, not an empty one. **Existing codebase (brownfield):** `/audit` first so every skill understands your project, then `/scope` the next slice on top of what exists, then the feature loop. **Any single change:** run only what it needs. A bug goes straight to `/debug`. A small change can be `/develop` then `/check verify`. **Monorepo:** everything scopes to the target workspace, which has its own AGENTS.md, scope, stack, and commands. ### The feature loop ``` /architect → /develop → /check verify → /test → /check review → /document → /sync ``` At the end of `/scope` you also pick a **workflow depth** for the project (override per feature anytime): `Prototype` (just `/develop`, self-checked, for throwaway work), `Alpha` (adds `/check verify`), `Beta` (adds `/test`), or `GA` (adds a fresh-model `/check review` and `/document`). The depth is a *suggested* checking tail after `/develop`, never a track you're locked onto: you're in charge, you run or skip any step and mark a feature `done` when you decide it is. The one t
Excerpt of 8,719 characters
Read on GitHub
118
10
1
Would you bet a product on this? Bounded 0–100 and slow moving.
matched fp:16abcb882b07b079, topic:agentic-ai, topic:agentic-workflow, desc:agentic