@ai-content-space/loopx 0.1.0 → 0.1.1

package/templates/architecture.md

@@ -6,11 +6,11 @@ decision_id: loopx-v1
 chosen_option: skill-first-runtime-substrate
 ---
 
-# LoopX Architecture: <task name>
+# loopx Architecture: <task name>
 
 ## Intent
 
-- keep LoopX skill-first while reusing the deterministic runtime/debug substrate
+- keep loopx skill-first while reusing the deterministic runtime/debug substrate
 
 ## Boundaries
 
@@ -21,7 +21,7 @@ chosen_option: skill-first-runtime-substrate
 
 ## Chosen Design
 
-- canonical LoopX artifacts under `.LoopX/`
+- canonical loopx artifacts under `.loopx/`
 - single build lane, no public `team`
 - bounded `autopilot` composition over clarify/plan/build/review
 

package/templates/development-plan.md

@@ -6,7 +6,7 @@ execution_mode_readiness: build
 stage_owner: plan
 ---
 
-# LoopX Development Plan: <task name>
+# loopx Development Plan: <task name>
 
 ## Execution Breakdown
 

package/templates/execution-record.md

@@ -12,7 +12,7 @@ checkpoint_count: <checkpoint count>
 evidence_manifest: [{"id":"<evidence id>","kind":"artifact","summary":"<summary>","ref":"<ref>"}]
 ---
 
-# LoopX Execution Record: <task name>
+# loopx Execution Record: <task name>
 
 ## Changes
 

package/templates/plan.md

@@ -6,15 +6,15 @@ source_spec_path: spec.md
 stage_owner: plan
 ---
 
-# LoopX Plan: <task name>
+# loopx Plan: <task name>
 
 ## Requirements Summary
 
-- translate the approved LoopX spec into an execution-ready package
+- translate the approved loopx spec into an execution-ready package
 
 ## Deliverables
 
-1. produce the LoopX plan package
+1. produce the loopx plan package
 2. keep approvals explicit
 3. define verification that can prove the run is ready for build
 
@@ -26,7 +26,7 @@ stage_owner: plan
 
 ## Risks
 
-- skipping approval or verification would break the LoopX contract
+- skipping approval or verification would break the loopx contract
 
 ## Verification
 

package/templates/review-report.md

@@ -11,7 +11,7 @@ rollback_target: <rollback target>
 rollback_rationale: <rollback rationale>
 ---
 
-# LoopX Review Report: <task name>
+# loopx Review Report: <task name>
 
 ## Verdict
 

package/templates/spec.md

@@ -2,11 +2,27 @@
 schema_version: 1
 workflow_id: <workflow id>
 stage: clarify
+profile: <profile>
+target_ambiguity_threshold: <target ambiguity threshold>
+max_rounds: <max rounds>
+current_round: 0
+ambiguity_score: 1
+non_goals_resolved: false
+decision_boundaries_resolved: false
+pressure_pass_complete: false
 approval_status: requested
 unresolved_ambiguity_count: 1
 ---
 
-# LoopX Spec: <task name>
+# loopx Spec: <task name>
+
+## Intent
+
+- TODO: capture why this work matters.
+
+## Desired Outcome
+
+- TODO: describe the end state the user actually wants.
 
 ## Ambiguity List
 
@@ -18,7 +34,7 @@ unresolved_ambiguity_count: 1
 
 ## In Scope
 
-- TODO: record the work that belongs in this LoopX run.
+- TODO: record the work that belongs in this loopx run.
 
 ## Non-Goals
 
@@ -28,6 +44,26 @@ unresolved_ambiguity_count: 1
 
 - Human approval is required before `clarify -> plan`.
 
+## Constraints
+
+- TODO: record technical, business, or sequencing constraints.
+
 ## Success Criteria
 
 - TODO: record what makes the run plan-ready.
+
+## Assumptions Exposed
+
+- TODO: list assumptions that were surfaced and how they were resolved.
+
+## Brownfield Evidence vs Inference
+
+- TODO: separate what was observed in code/docs from what is still inferred.
+
+## Design Direction
+
+- TODO: record the preferred shape or option if the task needed design guidance.
+
+## Next Handoff Recommendation
+
+- default: `plan`

package/templates/test-plan.md

@@ -5,7 +5,7 @@ stage: plan
 verification_checklist_status: drafted
 ---
 
-# LoopX Test Plan: <task name>
+# loopx Test Plan: <task name>
 
 ## Unit
 

package/plugins/loopx/skills/loopx-autopilot/SKILL.md

@@ -1,30 +0,0 @@
-# LoopX Autopilot
-
-## Purpose
-
-Repo-local bounded composition surface for LoopX. Use it when one owner wants the workflow to run end-to-end through clarify, plan, build, and review with the same stage gates still enforced.
-
-## Composition
-
-`loopx-autopilot` is a wrapper over:
-
-- `loopx-clarify`
-- `loopx-plan`
-- `loopx-build`
-- `loopx-review`
-
-## Decision Boundary
-
-- Use this when the task should stay on the repo-local LoopX path from ambiguity reduction through acceptance.
-- Stop at the first blocked stage. `loopx-autopilot` does not bypass approvals or continue past failed verification.
-
-## Must Not Decide Automatically
-
-- skipping a stage gate because the downstream task looks obvious
-- switching into a `team` lane or any parallel multi-agent dependency
-- treating CLI helpers as the primary product surface
-
-## Notes
-
-- `loopx-autopilot` is intentionally bounded. It documents composition over the four repo-local LoopX stages only.
-- The CLI remains supporting runtime and debug tooling, not the main release surface.

package/plugins/loopx/skills/loopx-build/SKILL.md

@@ -1,25 +0,0 @@
-# LoopX Build
-
-## Purpose
-
-Repo-local execution surface for LoopX. Use it to implement an approved plan and capture fresh verification evidence for the current run.
-
-## Expected Outputs
-
-- execution artifacts for the active LoopX run
-- verification evidence tied to the implementation run
-- stage status that shows readiness or blockers for review
-
-## Decision Boundary
-
-- Use this only after planning is complete and approved.
-- Stop here if execution or verification is incomplete. `loopx-build` can recommend follow-up work, but it does not self-approve review.
-
-## Must Not Decide Automatically
-
-- review approval
-- rollback or completion decisions
-
-## Notes
-
-- `loopx-build` is the active release execution surface. There is no public `team` execution lane in this repo-local skill set.

package/plugins/loopx/skills/loopx-clarify/SKILL.md

@@ -1,25 +0,0 @@
-# LoopX Clarify
-
-## Purpose
-
-Repo-local clarify surface for LoopX. Use it to turn a vague request into an execution-ready spec before planning or build work starts.
-
-## Expected Outputs
-
-- a clarify spec under the LoopX workspace
-- an explicit ambiguity list with unresolved items called out
-- stage status that makes the next action visible
-
-## Decision Boundary
-
-- Use this first when scope, acceptance, constraints, or verification are still unclear.
-- Stop here if unresolved ambiguity remains. `loopx-clarify` does not advance into planning on its own.
-
-## Must Not Decide Automatically
-
-- approval to move from clarify into plan
-- implementation details that were not established in the clarify output
-
-## Notes
-
-- This is a skill-first surface. Any CLI entrypoints are supporting runtime or debug helpers, not the primary product surface.

package/plugins/loopx/skills/loopx-plan/SKILL.md

@@ -1,25 +0,0 @@
-# LoopX Plan
-
-## Purpose
-
-Repo-local planning surface for LoopX. Use it to turn an approved clarify result into a concrete execution package.
-
-## Expected Outputs
-
-- a plan package under the LoopX workspace
-- explicit architecture, execution, and verification guidance
-- stage status that shows whether build is unblocked
-
-## Decision Boundary
-
-- Use this only after clarify has produced a usable spec.
-- Stop here if the plan package is incomplete or still awaiting approval. `loopx-plan` does not start execution on its own.
-
-## Must Not Decide Automatically
-
-- whether to skip straight to implementation without a complete plan
-- whether execution is approved
-
-## Notes
-
-- Keep the output artifact-bound and implementation-grounded. The plan should feed `loopx-build` or `loopx-autopilot`, not invent a separate workflow surface.

package/skills/loopx-autopilot/SKILL.md

@@ -1,30 +0,0 @@
-# LoopX Autopilot
-
-## Purpose
-
-Repo-local bounded composition surface for LoopX. Use it when one owner wants the workflow to run end-to-end through clarify, plan, build, and review with the same stage gates still enforced.
-
-## Composition
-
-`loopx-autopilot` is a wrapper over:
-
-- `loopx-clarify`
-- `loopx-plan`
-- `loopx-build`
-- `loopx-review`
-
-## Decision Boundary
-
-- Use this when the task should stay on the repo-local LoopX path from ambiguity reduction through acceptance.
-- Stop at the first blocked stage. `loopx-autopilot` does not bypass approvals or continue past failed verification.
-
-## Must Not Decide Automatically
-
-- skipping a stage gate because the downstream task looks obvious
-- switching into a `team` lane or any parallel multi-agent dependency
-- treating CLI helpers as the primary product surface
-
-## Notes
-
-- `loopx-autopilot` is intentionally bounded. It documents composition over the four repo-local LoopX stages only.
-- The CLI remains supporting runtime and debug tooling, not the main release surface.

package/skills/loopx-build/SKILL.md

@@ -1,25 +0,0 @@
-# LoopX Build
-
-## Purpose
-
-Repo-local execution surface for LoopX. Use it to implement an approved plan and capture fresh verification evidence for the current run.
-
-## Expected Outputs
-
-- execution artifacts for the active LoopX run
-- verification evidence tied to the implementation run
-- stage status that shows readiness or blockers for review
-
-## Decision Boundary
-
-- Use this only after planning is complete and approved.
-- Stop here if execution or verification is incomplete. `loopx-build` can recommend follow-up work, but it does not self-approve review.
-
-## Must Not Decide Automatically
-
-- review approval
-- rollback or completion decisions
-
-## Notes
-
-- `loopx-build` is the active release execution surface. There is no public `team` execution lane in this repo-local skill set.

package/skills/loopx-clarify/SKILL.md

@@ -1,25 +0,0 @@
-# LoopX Clarify
-
-## Purpose
-
-Repo-local clarify surface for LoopX. Use it to turn a vague request into an execution-ready spec before planning or build work starts.
-
-## Expected Outputs
-
-- a clarify spec under the LoopX workspace
-- an explicit ambiguity list with unresolved items called out
-- stage status that makes the next action visible
-
-## Decision Boundary
-
-- Use this first when scope, acceptance, constraints, or verification are still unclear.
-- Stop here if unresolved ambiguity remains. `loopx-clarify` does not advance into planning on its own.
-
-## Must Not Decide Automatically
-
-- approval to move from clarify into plan
-- implementation details that were not established in the clarify output
-
-## Notes
-
-- This is a skill-first surface. Any CLI entrypoints are supporting runtime or debug helpers, not the primary product surface.

package/skills/loopx-plan/SKILL.md

@@ -1,25 +0,0 @@
-# LoopX Plan
-
-## Purpose
-
-Repo-local planning surface for LoopX. Use it to turn an approved clarify result into a concrete execution package.
-
-## Expected Outputs
-
-- a plan package under the LoopX workspace
-- explicit architecture, execution, and verification guidance
-- stage status that shows whether build is unblocked
-
-## Decision Boundary
-
-- Use this only after clarify has produced a usable spec.
-- Stop here if the plan package is incomplete or still awaiting approval. `loopx-plan` does not start execution on its own.
-
-## Must Not Decide Automatically
-
-- whether to skip straight to implementation without a complete plan
-- whether execution is approved
-
-## Notes
-
-- Keep the output artifact-bound and implementation-grounded. The plan should feed `loopx-build` or `loopx-autopilot`, not invent a separate workflow surface.