@sireai/optimus 0.1.30 → 0.1.33

package/task-harnesses/pm/STANDARD.md

@@ -0,0 +1,125 @@
+# STANDARD
+
+## Execution loop
+- start from requirement input, not visual polish
+- identify the minimum prototype scope that makes the core flow reviewable
+- convert requirement meaning into interaction structure, page flow, and visible states
+- produce one reviewable prototype package
+- surface assumptions and open questions explicitly
+
+## Prototype rule
+- the primary artifact is an interactive HTML prototype
+- the prototype must make the main user flow inspectable
+- static page output alone is not enough unless the task is explicitly analysis-only
+- prioritize depth on the core path over shallow breadth
+- simulate product behavior lightly; do not pretend to implement production systems
+
+## Scope rule
+- stay within the accepted prototype scope
+- if the requirement is broad, reduce coverage to the most important flow
+- if key detail is missing, make only the minimum assumption needed for continuity
+- if trustworthy prototyping would require invention beyond the requirement basis, stop at analysis
+
+## Runtime contract
+- return exactly one runtime JSON object
+- normal prototype completion returns `completed`
+- analysis-only closure also returns `completed`
+- return `failed` only when execution itself fails
+- `resultPath` must point to exactly one file under `artifactDir`
+- `resultPath` must point to `result.md`
+- do not output prose outside the runtime JSON object
+
+### Example
+```json
+{
+  "status": "completed",
+  "resultPath": "result.md"
+}
+```
+
+## Result artifacts
+- always generate `result.md` on normal completion
+- supporting files are task-private outputs placed under `artifactDir`
+- generate `prototype.html` for `Prototype Complete` and `Prototype Partial`
+- use repository-independent artifact paths
+- `result.md` is the only framework-required result artifact
+- private output files must be declared inside `result.md`
+
+## Closure target
+Use exactly one closure level:
+- `Prototype Complete`
+- `Prototype Partial`
+- `Analysis Only`
+
+## Result content
+At minimum, `result.md` must include:
+
+### Delivery Summary
+- `Closure`
+- `Prototype Scope`
+- `Core Flow`
+- `Platform`
+- `Coverage`
+- `Assumptions`
+- `Open Questions`
+- `Next Action`
+
+### Outputs
+- `Main Review Artifact`
+- `Additional Files`
+- `Output Notes`
+
+### Detail
+- `Product Goal`
+- `Target User`
+- `Requirement Summary`
+- `Covered Screens / Sections`
+- `Key Interactions`
+- `States Included`
+- `Assumptions`
+- `Open Questions`
+- `Recommended Next Step`
+
+## Content rules
+- clearly separate confirmed requirement content from inferred structure
+- do not hide missing requirement detail inside polished prototype output
+- keep summaries dense and review-oriented
+- prefer explicit gaps over fake completeness
+- if prototype output is produced, declare its path under `Outputs`
+- if no prototype output is produced, state `Main Review Artifact: not produced` and explain why
+
+## Result template
+Use this as the minimum `result.md` shape on normal completion:
+
+```md
+# Delivery Summary
+- Closure: Prototype Complete
+- Prototype Scope: First-run onboarding only
+- Core Flow: Open invite -> fill profile -> complete setup
+- Platform: responsive
+- Coverage: invite landing, profile form, completion state
+- Assumptions: invite is valid for one user session
+- Open Questions: SSO is optional or required?
+- Next Action: review flow coverage and copy gaps
+
+# Outputs
+- Main Review Artifact: `prototype.html`
+- Additional Files: none
+- Output Notes: private outputs live under `artifactDir`
+
+# Detail
+- Product Goal: Reduce first-day confusion
+- Target User: New employee
+- Requirement Summary: Requirement input asks for a reviewable onboarding prototype
+- Covered Screens / Sections: invite landing, profile setup, confirmation
+- Key Interactions: start onboarding, form validation, submit, success transition
+- States Included: empty, validation error, loading, success
+- Assumptions: backend behavior is simulated only
+- Open Questions: whether manager approval is required before activation
+- Recommended Next Step: confirm approval rule and add branch state if needed
+```
+
+## Closure policy
+- `Prototype Complete`: the accepted scope is covered by a coherent interactive prototype
+- `Prototype Partial`: a meaningful prototype exists, but coverage is incomplete
+- `Analysis Only`: no trustworthy prototype was produced; explain blockers and missing input

package/task-harnesses/pm/manifest.json

@@ -0,0 +1,13 @@
+{
+  "id": "pm",
+  "triageRules": [
+    "ACCEPT.md"
+  ],
+  "executionRules": [
+    "ROLE.md",
+    "CONSTRAINTS.md",
+    "CONTEXT.md",
+    "STANDARD.md",
+    "EVOLUTION.md"
+  ]
+}

package/task-harnesses/registry.json

@@ -3,6 +3,10 @@
     {
       "taskType": "bugfix",
       "dir": "bugfix"
+    },
+    {
+      "taskType": "pm",
+      "dir": "pm"
     }
   ]
 }