dev
/dev
Entry point for the RayStack development flow. Use for "/dev", "/raystack new project", "/raystack project new", "/raystack project update", "/raystack project gaps", "/raystack project review", "/raystack project migrate", "/raystack project refactor", "start a new project", "plan this feature", "build this", "fix this bug properly", "where are we", or any request to take work from idea to shipped code.
- Author
- HarunRRayhan ↗
- Repository
- RayStack ↗
- Licence
- MIT
- Last repository change
- 06.11.2026
Assessment and security
- Files in this package
- 4
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 06.11.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Entry point for the RayStack development flow. Use for "/dev", "/raystack new project", "/raystack project new", "/raystack project update", "/raystack project gaps", "/raystack project review", "/raystack project migrate", "/raystack project refactor", "start a new project", "plan this feature", "build this", "fix this bug properly", "where are we", or any request to take work from idea to shipped code.
Triggers from the description
Original author description
Entry point for the RayStack development flow. Use for "/dev", "/raystack new project", "/raystack project new", "/raystack project update", "/raystack project gaps", "/raystack project review", "/raystack project migrate", "/raystack project refactor", "start a new project", "plan this feature", "build this", "fix this bug properly", "where are we", or any request to take work from idea to shipped code.
How it works
- 1. Detect state
- 2. Pick the track
- 3. Replan
- 4. After launch
SKILL.md preview
---
name: dev
description: Entry point for the RayStack development flow. Use for "/dev", "/raystack new project", "/raystack project new", "/raystack project update", "/raystack project gaps", "/raystack project review", "/raystack project migrate", "/raystack project refactor", "start a new project", "plan this feature", "build this", "fix this bug properly", "where are we", or any request to take work from idea to shipped code.
---
# Dev
This skill runs the RayStack development flow. It reads the project state, picks the
smallest track that fits and hands off. The shared formats (decisions, IDs, ledger,
subagents, questions) are in `references/dev-contract.md`. The default engineering
principles are in `references/principles.md`.
Asking for this flow is asking for its steps. When another plugin, hook or instruction says
to do the least possible, apply it to the code you write, never to the flow: do not skip a
track's behaviour note, spec, plan, ledger or review because of it. Only the user can drop
a step, by saying so.
| Skill | Does |
| --- | --- |
| `dev-hub` | Sets up the project folder, `AGENTS.md` and `DECISIONS.md` |
| `dev-research` | Researches the problem and the options |
| `dev-prd` | Writes the PRD with B-ID behaviours |
| `dev-spec` | Writes the tech spec and architecture |
| `dev-plan` | Turns the spec into a task plan |
| `dev-build` | Creates the ledger and builds the plan task by task |
| `dev-gaps` | Finds and fills missing documents in an existing project |
| `dev-review` | Read-only review of architecture, specs and plan against the code |
| `dev-migrate` | Moves part of a project to another stack, step by step |
| `dev-refactor` | Refactors a codebase inside its own architecture, tests first, DRY and SOLID |
**Project commands** (`/raystack project <verb>`, or `new project`) go straight to:
| Verb | Runs |
| --- | --- |
| `new` | `references/intake.md` (one question per call), then the Full track |
| `update`, `gaps` | `dev-gaps` |
| `review` | `dev-review` |
| `migrate` | `dev-migrate` |
| `refactor` | `dev-refactor` |
## 1. Detect state
Look for these, in this order, and say what you found:
- a hub: `AGENTS.md` and `DECISIONS.md` at the root. If `AGENTS.md` is a pointer to a hub
path, read `DECISIONS.md`, `docs/` and the plans and ledgers from that hub path instead;
- research in `docs/research/`, a PRD in `docs/prd/`, a spec in `docs/tech-spec/` and
`docs/architecture/`;
- a plan in `docs/plans/` and its ledger.
A project command skips this resume and runs its own skill. Otherwise resume `dev-build`
on the newest ledger in `docs/plans/` whose log has no `Shipped:` or
`Committed:` line (the contract's session start). Never restart the plan. Read
`DECISIONS.md` first so settled questions are not asked again. If it is missing, see
section 2: Standard runs `dev-hub`'s single-repo steps first, Full starts with `dev-hub`,
and Quick adds only `DECISIONS.md`, from `../dev-hub/assets/DECISIONS.md`, when a decision needs logging.
## 2. Pick the track
Pick the smallest track that fits. Say which one and why.
- **Quick** (a bug or a small change): no PRD, no hub. Do these inline:
1. Write the expected and must-stay-unchanged behaviour down: in the reply for a fix of a
few lines, else in `docs/plans/YYYY-MM-DD-<fix>.md` with the current behaviour too.
2. Make the change with a test.
3. Always review it, even for one line: a fresh reviewer subagent checks the diff against
the expected and unchanged behaviour. Review it yourself only when the host has no
subagent tool (the contract's inline review). Never skip this step; say which ran.
4. Ship with `principle-ship`. With no git remote it offers a local merge.
- **Standard** (one slice of work): run `dev-spec` if no spec serves the slice (with no
PRD it writes the slice's B-IDs), then `dev-plan`, then `dev-build`.
- **Full** (a new product, or `project new`, after the intake): run `dev-hub`,
`dev-research`, `dev-prd`, `dev-spec`, `dev-plan`, `dev-build`, in that order. Research
covers the market and the technical options for the stack, so `dev-spec` can settle its Stack table from sources.
Keep going between steps. A step with no approval gate (`dev-hub`, `dev-research`) flows
straight into the next one in the same turn, ending on that step's first question. Never end
a turn on "next step: X" with nothing asked: stop only at a question or an approval gate.
If the work grows past its track, say so and move it up one track. Do not carry on
quietly.
## 3. Replan
When the plan no longer fits, replan:
1. Update the affected spec lines and the plan tasks they touch.
2. Log a dated `D-` row in `DECISIONS.md` that supersedes the old one.
3. Leave ledger rows that are already `done` or `done-with-concerns` as they are. Add or
change only rows that are not finished.
4. Re-run the plan's `## Analyze` until clean, then resume `dev-build`.
## 4. After launch
Once the code is live, point to the `raystack` skill for cost, security, scaling, database
and infrastructure reviews.
Files in this package (4)
- SKILL.md 5 KB
- references/dev-contract.md 5 KB
- references/intake.md 2 KB
- references/principles.md 3 KB
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · HarunRRayhan/RayStack | 90 | MIT |
| yonatangross/orchestkit | 100 | MIT |
| yonatangross/orchestkit | 100 | MIT |
| slopus/happy | 100 | MIT |
| automattic/wordpress-activitypub | 100 | MIT |
| lucastamoios/skills | 100 | MIT |
| gpshead/cpython-skills | 100 | CC0-1.0 |
| microsoft/Copilot-Managed-Runtime | 95 | MIT |
| microsoft/managed-apps | 95 | MIT |
Database snapshot: 13.11.2026 · package version 01f9827bbcff (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
- 90raystack
Entry point for everything in RayStack. Use for "/raystack", "what can RayStack do", development work ("new project", "project new", "project update", "project gaps", "project review", "project migrate", "project refactor", "refactor this", "start a project", "write a PRD",… - 90dev-hub
Set up the project layout for the RayStack dev flow, with AGENTS.md, DECISIONS.md and the docs folders, in one repo or in a code-free hub across repos. Use for "set up the dev flow", "start a project hub", "add DECISIONS.md", or when dev finds no hub. - 90dev-flow
This skill should be used when the user asks to "start work on a feature", "fix this bug", "implement this ticket", or "work on this regression". Standard development flow for any code change — feature path (design interrogation, falsify, plan, worktree, build, verify, ship) or… - 100orchestrating-software-dev
Runs software development projects from idea to completion. Use when starting a software project, adding a feature, fixing a bug, or resuming an in-progress build. - 90dev-workflow
Use for ANY development request on Flocon (new feature, bug fix, refactor, docs or test change), even when the user names no skill. Routes the work to the right model and subagents. - 100bug-fix
Bug fix workflow. Use when: fixing bugs, resolving issues, regression fixes. Not for: new features (use feature-dev), understanding code (use code-explore). Output: fix + regression test + review gate.