drive-development-flow
Select the next software workflow when defining, implementing, reviewing, or resuming development work.
- License 许可
- MIT
- 最近更新
- 2026-11-14
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- drive-development-flow
- description
- Select the next software workflow when defining, implementing, reviewing, or resuming development work.
03 SKILL.md 正文
Development flow
Optimize rápido → bien → barato: time to the complete usable outcome, including corrections. Recover the outcome, settled decisions and authorized endpoint from the current request and available project context. Follow-ups steer that outcome unless the user replaces it.
Choose only the current stage
- Clear implementation or a bug fix: proceed with
flow-implement. A small, obvious edit can be handled directly with applicable repository checks. - Approved specification: use
implement-specwhen coordinating its scope or ticket dependencies; reuse the existing spec instead of defining it again. - Requested discovery or questioning: use
grill-with-docs. Useworking-backwardsfor a requested PRFAQ or staged product definition. - New visual direction or an approved design handoff: use
design-direction. A small visual refinement stays in Impeccable's matching workflow. - Branch/diff review: use
flow-code-review. Review of a thread's claims and execution history: usereview-thread. - Explanation or status: answer from relevant sources; this does not start implementation or require a generated document.
Load the applicable branch, not this entire list. For non-trivial repository
execution, coding-orchestration owns delegation and verification. A worker
with an exact root, task and checks executes its packet; it does not repeat
parent routing. A supplied orchestrate-work execution method can satisfy that
responsibility without loading a second coordination stack.
Continue through the agreed endpoint
Make completion observable: requested behavior, relevant checks, unresolved acceptance criteria and the delivery surface. Reuse the existing task record; an ordinary edit needs no new planning document. Continue implementation, verification and corrections already authorized. A first draft or a worker's completion is not the user's complete result.
Retain authorization across turns. Prepare the concrete, reviewable result before requesting a genuinely missing authorization for a distinct operation. Preserve repository protections and host permission boundaries; authority for one operation does not automatically authorize another. Continue independent work when a dependency is blocked.
Current user instructions supersede skill guidelines. If a skill actually prevents authorized progress, link its exact file, quote the applicable rule and explain the missing decision; do not invent an approval requirement.
04 同仓库更多 Skills
working-backwards
Define a software feature through PRFAQ and staged documents when the user requests working backwards before coding.
flow-implement
Implement a requested software change through verification, corrections, and its authorized delivery endpoint.
development-steward
Run the scheduled, read-only weekly maintenance review for the six explicitly opted-in repositories and prepare one concise private report for Check-in.
grill-with-docs
Run one recoverable interview for functional, visual, or mixed software grills; reuse equivalent answers and offer the shared HTML questionnaire.
global-agent-guardrails
Install, audit, test, or update the Development System's global destructive-command guard for Codex, Claude Code and T3 Code. Use when configuring agent safety hooks or investigating whether dangerous shell operations are blocked.
impeccable
Design or refine frontend UI using project context and a focused design playbook; also handles visual critique and polish.