development-flow-loop

星标1

分支0

更新时间2026年4月2日 23:21

Structured software delivery lifecycle for coding tasks that should move from planning to production with repeated quality gates. Use when building features, refactors, integrations, automations, or systems work where the expected flow is Plan, Architect, Evaluate, Implement, Test, Fix, Test, Improve, Test, Fix or Launch, Launch.

安装

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

来源

issdandavis

issdandavis/scbe-aethermoore-demo

打开 GitHub 仓库查看创作者相关仓库

下载

Development Flow Loop

Overview

Follow this exact execution loop for development work. Advance only when each stage gate is satisfied.

Lifecycle

Plan

Define objective, constraints, dependencies, risks, and success criteria.
Output: concise plan with explicit deliverables.

Architect

Choose structure, interfaces, data flow, and failure boundaries.
Output: implementation shape and file ownership.

Evaluate

Critique the design before coding: complexity, maintainability, testability, cost, and safety.
Output: go/no-go with concrete adjustments.

Implement

Ship the minimum correct version first.
Keep changes scoped; avoid unrelated edits.

Test

Run targeted tests first, then broader checks if needed.
Output: pass/fail evidence.

Resolve failures from step 5 with minimal blast radius.

Test

Re-run relevant tests until stable.

Improve

Upgrade quality after stability: readability, performance, docs, ergonomics, observability.

Test

Validate improvements did not regress behavior.

Fix or Launch Decision

If red or risky: fix and return to Test.
If green and acceptable risk: prepare launch.

Launch

Publish/deploy/release with verification and rollback awareness.
Output: release confirmation and post-launch check result.

Operating Rules

Prefer small increments and frequent validation over large untested changes.
Keep a clear audit trail: what changed, why, what proved it works.
If blocked, reroute quickly, then merge best parts back into one path.
Treat this flow as iterative: repeat Fix -> Test -> Improve -> Test as needed.

同仓库更多 Skills

同仓库

aether-phone-lane-ops

issdandavis/scbe-aethermoore-demo

Boot, recover, tune, and verify the SCBE Android emulator phone lane for AetherCode and Polly Pad. Use when Codex needs to operate the `SCBE_Pixel_6_API35` emulator, repair stale lock state, resize the phone surface, or prove the current lane state from local artifacts.

2026-04-021

aetherbrowser-arxiv-nav

issdandavis/scbe-aethermoore-demo

Navigate arXiv papers and topic searches through AetherBrowser for research extraction workflows. Use when collecting abstracts, paper metadata, and evidence snapshots from arxiv.org.

2026-04-021

aetherbrowser-github-nav

issdandavis/scbe-aethermoore-demo

Navigate GitHub repositories, pull requests, issues, and settings through AetherBrowser tentacle routing. Use when tasks require browser-based GitHub movement, page evidence capture, or coordinated lane assignment with playwriter or playwright.

2026-04-021

aetherbrowser-huggingface-nav

issdandavis/scbe-aethermoore-demo

Navigate Hugging Face models, datasets, and spaces through AetherBrowser for research, validation, and publishing workflows. Use when inspecting repo cards, files, docs, and leaderboard surfaces in browser mode.

2026-04-021

aetherbrowser-notion-nav

issdandavis/scbe-aethermoore-demo

Navigate Notion workspace pages in AetherBrowser for knowledge retrieval and workspace coordination tasks. Use when locating pages, databases, or section paths in browser mode before API operations.

2026-04-021

aetherbrowser-operator

issdandavis/scbe-aethermoore-demo

Operate AetherBrowser as the primary online task surface across search, GitHub, Codespaces, research, Notion, Hugging Face, Shopify, and general web work. Use when Codex should drive a real browser session first, coordinate with built-in search or fetch tools second, capture page-state proof, and keep online work inside the SCBE browser lane instead of defaulting to generic web automation.

2026-04-021

name	development-flow-loop
description	Structured software delivery lifecycle for coding tasks that should move from planning to production with repeated quality gates. Use when building features, refactors, integrations, automations, or systems work where the expected flow is Plan, Architect, Evaluate, Implement, Test, Fix, Test, Improve, Test, Fix or Launch, Launch.

Development Flow Loop

Overview

Follow this exact execution loop for development work. Advance only when each stage gate is satisfied.

Lifecycle

Plan

Define objective, constraints, dependencies, risks, and success criteria.
Output: concise plan with explicit deliverables.

Architect

Choose structure, interfaces, data flow, and failure boundaries.
Output: implementation shape and file ownership.

Evaluate

Critique the design before coding: complexity, maintainability, testability, cost, and safety.
Output: go/no-go with concrete adjustments.

Implement

Ship the minimum correct version first.
Keep changes scoped; avoid unrelated edits.

Test

Run targeted tests first, then broader checks if needed.
Output: pass/fail evidence.

Resolve failures from step 5 with minimal blast radius.

Test

Re-run relevant tests until stable.

Improve

Upgrade quality after stability: readability, performance, docs, ergonomics, observability.

Test

Validate improvements did not regress behavior.

Fix or Launch Decision

If red or risky: fix and return to Test.
If green and acceptable risk: prepare launch.

Launch

Publish/deploy/release with verification and rollback awareness.
Output: release confirmation and post-launch check result.

Operating Rules

Prefer small increments and frequent validation over large untested changes.
Keep a clear audit trail: what changed, why, what proved it works.
If blocked, reroute quickly, then merge best parts back into one path.
Treat this flow as iterative: repeat Fix -> Test -> Improve -> Test as needed.