Closed-loop Development
Coordinate development, testing, defect fixes, regression, and review based on confirmed requirements and implementable designs. Assess delivery status using complete user tasks and evidence.
Requirements
Targeted at Codex-like intelligent agents with repository and file access capabilities. The documentation does not provide access to browsers, testing tools, credentials, project data, or modifications to external systems. Other hosts may need adaptation.
- Confirmed requirements and applicable development, database, API, and interaction specifications
- Authorized code and test access capabilities, as well as the necessary real runtime environment and data
- Install the supporting Skills for the phase used. Adding or significantly modifying UI interactions requires the frontend-design-lab, which is not included with this package.
Quick start
- After downloading, check the instructions within the package and unzip the ZIP into a temporary directory.
- When installing the collection, copy the six Skill folders and the shared folder at the same level into the project's .agents/skills/ or the user's ~/.agents/skills/. Maintain the relative directory structure and do not install the collection's outer directory as a Skill.
- When installing a separate ZIP, place the folder with the same name into the chosen Skills directory and retain its internal shared resources. Back up any existing Skill with the same name before overwriting to avoid duplicate installation.
- Use the accurate $develop-closed-loop call in Codex. If it is not found, restart the host. If task handover requires the process, install the corresponding supporting Skill separately.
Applicable scenarios
- Move clearly designed features to acceptance
- Move larger deliverables forward while maintaining item-level requirement progress and blockers
Steps to use
- Invoke $develop-closed-loop, providing authoritative requirements, design, scope, and permissions. First, resolve decision-making on blocked implementations, then proceed with coding that depends on them.
- Establish a mapping from REQ/AC to implementation, use cases, regression evidence, review, and status, and proceed according to complete small user paths.
- Implement, test, categorize failures, execute authorized fixes, regress related paths, and review recent differences. Return to the corresponding stage if there are still defects.
- Validate UI tasks in a real browser or target application, including applicable refreshes or reopens. Verify all scope and required delivery checks before reporting status.
Field naming and page text
Requirements, front-end and back-end fields, pages, interfaces, and exports follow common, accurate, and consistent business names. Clearly display label and existing identifier mappings without breaking public contracts by changing display names. Pages do not add unexplained explanations by default, nor move explanations to placeholders, tooltips, or collapsible areas. Necessary labels, validations, status, error, and recovery feedback are preserved as usual. A separate ZIP includes the required shared reference.
Delivery contents
- Progress records from requirements to evidence and actual implementation changes
- When supported by evidence, separately report that something has been implemented, locally verified, deployed, or accepted in the real online path
Limitations
- Standalone downloads are not a complete development toolkit and may require other supporting processes.
- Without product decisions, real verification conditions, or necessary reviews, it is not possible to declare full completion.
- The process itself does not authorize deployment, addition of functionality, replacement of acceptance data, or generation of external side effects.
Example prompt, not an actual execution case
Use $develop-closed-loop to implement the approved personal profile editing requirements based on existing design. Maintain scope and visual system, verify the results of saving and reopening in an authorized test environment, list blocked requirements separately, and do not deploy.
This guide describes workflows within the package and does not represent validated cross-model reliability or an actual acceptance operational report.
--- name: develop-closed-loop license: MIT description: >- Once requirements, development design, and applicable database/API/interaction specifications are ready, continue development, testing, repair, regression, and code review until the user-confirmed scope has complete delivery evidence. Do not add or remove features independently. Pause for material product decisions; advance routine implementation under existing authorization. --- # Closed-Loop Development Completion is measured by user-confirmed requirements and complete tasks, not commit counts, module counts, or green tests. Development, testing, defect repair, regression, and code review are parts of the loop. Do not manufacture a repair when no defect exists; return to the appropriate phase until actual issues are closed. Load `talking-us`, `write-design-doc`, `test-case`, `bug-fixing`, and `code-review-multiagent` by phase. Prefer a user-specified version, otherwise the currently enabled entry point. Handoffs reference the same task record and carry original scope, decisions/unresolved dependencies, data and side-effect permissions, specified execution medium, existing style, version, and coverage gaps. Invoking a skill neither resets constraints nor grants permission. ## 1. Start Gate: Implementable Specifications, Unchanged Scope
develop-closed-loop/LICENSE develop-closed-loop/MANIFEST.json develop-closed-loop/README.md develop-closed-loop/SKILL.md develop-closed-loop/agents/openai.yaml develop-closed-loop/references/delivery-gates.md develop-closed-loop/references/product-release-validation.md develop-closed-loop/shared/product-language.md