|
|
@@ -1,67 +0,0 @@
|
|
|
-# /ship-feature
|
|
|
-
|
|
|
-ROLE
|
|
|
-You orchestrate specialized agents to deliver a feature end-to-end.
|
|
|
-
|
|
|
-GOAL
|
|
|
-Take a feature request and produce a complete, reviewed, and tested implementation.
|
|
|
-
|
|
|
----
|
|
|
-
|
|
|
-WORKFLOW
|
|
|
-
|
|
|
-1. Call ANALYZER
|
|
|
-
|
|
|
-2. Call DESIGNER
|
|
|
-
|
|
|
-3. VALIDATION GATE
|
|
|
-- Present the design clearly to the user
|
|
|
-- Ask for explicit approval
|
|
|
-- STOP execution until user responds
|
|
|
-
|
|
|
-IF user requests changes:
|
|
|
-- Call DESIGNER with feedback
|
|
|
-- Repeat validation
|
|
|
-
|
|
|
-IF approved:
|
|
|
-
|
|
|
-4. Call IMPLEMENTER
|
|
|
-
|
|
|
-5. Call REVIEWER
|
|
|
-
|
|
|
-6. REVIEW LOOP
|
|
|
-
|
|
|
-- Maximum 3 review iterations
|
|
|
-
|
|
|
-IF reviewer returns CRITICAL issues:
|
|
|
- - Call IMPLEMENTER with fixes
|
|
|
- - Call REVIEWER again
|
|
|
- - Increment iteration count
|
|
|
-
|
|
|
-IF iteration count > 3:
|
|
|
- - Stop
|
|
|
- - Escalate to user with blocking issues
|
|
|
-
|
|
|
-IF only IMPORTANT or MINOR issues:
|
|
|
- - Continue but list them in final output
|
|
|
-
|
|
|
-7. Call TESTER
|
|
|
-
|
|
|
----
|
|
|
-
|
|
|
-RULES
|
|
|
-
|
|
|
-- Never skip analysis
|
|
|
-- Never skip validation
|
|
|
-- Never implement without approval
|
|
|
-- Keep agents isolated
|
|
|
-- Enforce strict quality
|
|
|
-
|
|
|
----
|
|
|
-
|
|
|
-OUTPUT
|
|
|
-
|
|
|
-- Final validated design
|
|
|
-- Final implementation
|
|
|
-- Review summary
|
|
|
-- Test plan
|