dev-flow

Plugin dev-flow from marketplace vincy-skills in vincy-cheng/skills. Commands read from the repo's manifest — 13 days ago.

Skills (15)

• bootstrap

  Use to prepare a repo for dev-flow in one pass — gitignore for the state folder, gh auth check, branch config (main + dev branch names persisted to .dev-flow/config.json), and agent docs via the document-structure engine. Triggers on "bootstrap this repo", "set up this repo for dev-flow", "prepare t

• brainstorm

  Use when designing or exploring a feature or fix before building it — turn an idea into a validated design and spec through collaborative dialogue. Runs standalone in any repo, or as the engine of dev-flow step 1 (invoked by the new-feature command).

• commit

  Use whenever the user wants to commit staged or current changes ("commit this", "make a commit", "save progress", "commit the work"). Writes a Conventional Commits message from the diff and commits. Can run standalone or as part of dev-flow step 5 (per-task commits during TDD execution). NEVER menti

• create-github-issue

  Use whenever the user wants to create, open, file, or draft a GitHub issue — "create an issue for X", "file a bug", "open an issue", "track this", "log this", or describes a feature/bug to track. Also when turning a conversation, bug report, or feature idea into a tracked issue. This is step 4 of th

• doc-fix

  Use to fix doc drift caused by the current run before opening its PR — dev-flow step 8. Scans this plugin's docs and the target repo's docs for text the run's changes just invalidated (behavior described the old way, a new convention not documented), shows the proposed edits for user confirmation, t

• document-structure

  Use to generate or update a repo's agent-facing docs — a layered progressive-disclosure tree under docs/agents/ (a tiny always-load index, core maps for architecture and dev-ops, plus dynamic concern maps discovered from the project — testing, API, deployment, database/SQL, auth, etc. — and optional

• execute-tasks

  Use to execute a dev-flow plan task by task. This is step 5 of the dev-flow workflow — work the plan's tasks with TDD (failing test → implement → green → commit per task), updating the state file as you go. The Implementer dispatches per the state file's Roles block lane: inline (runs in this sessio

• new-feature

  Start or resume a feature or fix through the complete dev-flow pipeline. Use when asked to build a feature, implement a change, or resume a dev-flow run.

• new-idea

  Use when the user asks to create / brainstorm an idea, scaffold an idea folder, or "put relevant docs" for a product/concept — creates a structured idea folder under ideas/ with a fixed set of five self-contained markdown docs (six when the user opts into a cost.md breakdown), including a draft plan

• open-pr

  Use to open a pull request for a feat or fix branch — dev-flow step 9 (after doc-fix, before the manual merge). Pushes, drafts the PR body (issue link, spec/plan summary, closing keyword), shows it for confirmation, opens with `gh pr create` targeting the state file's Target branch (`dev` by default

• plan

  Use when turning an approved spec or settled requirements into an implementation plan — bite-sized ordered tasks with files, TDD shape, and a flow chart. Runs standalone in any repo, or as the engine of dev-flow step 3 (invoked by the new-feature command).

• review

  Use to review a feat or fix branch before opening a PR — a judgment review gate checking spec coverage, plan coverage, obvious issues (bugs, security smells, leftover, naming), and maintainability with a clean-code pass (structure, coupling, naming, complexity, duplication, functions, conditionals,

• standardize-prose

  Standardize the prose language of a dev-flow spec or plan for human readers — a guided cleanup pass adapted from ASD-STE100 Simplified Technical English. Use when the user says "standardize this spec/plan", "clean up the language in this doc", "fix the terminology drift", or names a doc to polish. S

• tdd

  Use when implementing any feature or bugfix test-first, before writing implementation code — red-green loop, seams, test honesty. Runs standalone in any repo, or as the TDD engine of dev-flow step 5 (invoked by execute-tasks per task).

• whats-new

  Use to summarize what's new in a repo — recent shipped work AND current codebase state vs. its docs. Triggers on \"what's new\", \"what changed recently\", \"summarize recent work\", \"catch me up on this repo\". Returns a view (nothing written): history from git log + gh PRs/issues, plus a doc-drif

Slash commands (3)

• /dev-flow:bootstrap

  Prepare this repo for dev-flow in one pass — gitignore for the state folder, gh auth check, branch config (main + dev names persisted to .dev-flow/config.json), and agent docs via the document-structure engine. Idempotent per component; re-runs are green no-ops that double as a health check. Standal

• /dev-flow:new-feature

  Start a new feat or fix through the full workflow — plan (brainstorm → spec → plan → issue) → build (execute, TDD) → verify (test → review → doc-fix) → ship (PR → manual merge → close-out). 11 steps. Pass the idea as arguments; pass nothing or "resume" to continue prior work. Maintains gitignored st

• /dev-flow:new-idea

  Create a structured idea folder under ideas/<slug>/ (or ideas/<project>/<slug>/ in an ideas repo) with five self-contained docs — README, research, design, plan, tl-dr — plus cost.md when the user opts in. Asks two questions up front: nesting level, and whether to include cost research. Discusses an

Similar plugins