Add OpenAI skills from the some of SPECS/COMMANDS

.agents/skills/flow-primitive-commit/SKILL.md

@@ -0,0 +1,42 @@
+---
+name: flow-primitive-commit
+description: Create focused, scoped git commits for the current task. Use when the workflow requires committing work, when only specific files should be staged, when commit messages must be clear and present-tense, or when validating the worktree state before push/archive.
+---
+
+# Flow Primitive Commit
+
+Create a reliable commit snapshot that includes only files relevant to the active task.
+
+## Workflow
+
+1. Inspect status:
+
+```bash
+git status -sb
+```
+
+2. Stage only task-relevant files:
+
+```bash
+git add <files...>
+```
+
+3. Commit with a concise present-tense summary:
+
+```bash
+git commit -m "Add Web UI release task to workplan"
+```
+
+4. Verify post-commit state:
+
+```bash
+git status -sb
+```
+
+## Rules
+
+- Keep commits scoped to one task/PRD change.
+- Prefer explicit file staging over `git add .`.
+- Use present-tense commit subjects.
+- Split mixed deliverables into multiple commits when reviewability improves.
+- Do not amend or rewrite history unless explicitly requested.

.agents/skills/flow-primitive-commit/agents/openai.yaml

@@ -0,0 +1,4 @@
+interface:
+  display_name: "Commit Primitive"
+  short_description: "Create focused, scoped git commits for current task"
+  default_prompt: "Use the commit primitive workflow to stage relevant files and create a clear commit message."

.agents/skills/flow-run/SKILL.md

@@ -0,0 +1,89 @@
+---
+name: flow-run
+description: Run the complete task workflow for this repository by strictly following SPECS/COMMANDS/FLOW.md from BRANCH through ARCHIVE-REVIEW, including required commit checkpoints and quality gates. Use when asked to do the next task end-to-end, complete the full workflow, or execute "start to finish" task delivery in this project.
+---
+
+# Flow Run
+
+Execute the workflow in `SPECS/COMMANDS/FLOW.md` exactly, without skipping required steps unless the workflow itself explicitly allows skipping.
+
+## Required Inputs
+
+Collect these before starting:
+- Task identifier (for example `P5-T2`) and short description.
+- Current branch and whether a feature branch already exists.
+- Confirmation of which review subject name to use for `REVIEW_{subject}.md`.
+
+If the task identifier is unknown, determine it from `SPECS/Workplan.md` and `SPECS/INPROGRESS/next.md` during SELECT.
+
+## Execution Contract
+
+Apply these rules throughout execution:
+- Read `SPECS/COMMANDS/FLOW.md` at the beginning and treat it as the source of truth.
+- Complete steps in order: `BRANCH -> SELECT -> PLAN -> EXECUTE -> ARCHIVE -> REVIEW -> FOLLOW-UP -> ARCHIVE-REVIEW`.
+- Create a commit checkpoint after each major step using FLOW commit message patterns.
+- Run required quality gates during EXECUTE (`pytest`, `ruff check src/`, `mypy src/` if configured, `pytest --cov` with coverage >= 90%).
+- Record artifacts in expected locations under `SPECS/INPROGRESS/` and `SPECS/ARCHIVE/`.
+- If REVIEW has no actionable issues, skip FOLLOW-UP and proceed directly to ARCHIVE-REVIEW, as FLOW permits.
+
+## Step Procedure
+
+1. BRANCH
+- Ensure `main` is up to date.
+- Create `feature/{TASK_ID}-{short-description}` if not already on the correct feature branch.
+- Commit message pattern: `Branch for {TASK_ID}: {short description}`.
+
+2. SELECT
+- Choose the next task from `SPECS/Workplan.md` (optionally with `python scripts/pick_next_task.py`).
+- Update `SPECS/INPROGRESS/next.md` with selected task metadata.
+- Commit message pattern: `Select task {TASK_ID}: {TASK_NAME}`.
+
+3. PLAN
+- Create the task PRD at `SPECS/INPROGRESS/{TASK_ID}_{TASK_NAME}.md`.
+- Define deliverables, acceptance criteria, dependencies.
+- Commit message pattern: `Plan task {TASK_ID}: {TASK_NAME}`.
+
+4. EXECUTE
+- Implement to the PRD.
+- Run quality gates defined in FLOW.
+- Create `SPECS/INPROGRESS/{TASK_ID}_Validation_Report.md`.
+- Commit message pattern: `Implement {TASK_ID}: {brief description of changes}`.
+- Split into incremental commits if the task is large.
+
+5. ARCHIVE
+- Run `SPECS/COMMANDS/ARCHIVE.md` workflow.
+- Verify task archive folder exists under `SPECS/ARCHIVE/{TASK_ID}_{TASK_NAME}/`.
+- Confirm `SPECS/INPROGRESS/next.md` and `SPECS/Workplan.md` are updated.
+- Commit message pattern: `Archive task {TASK_ID}: {TASK_NAME} ({VERDICT})`.
+
+6. REVIEW
+- Run `SPECS/COMMANDS/REVIEW.md`.
+- Save review report at `SPECS/INPROGRESS/REVIEW_{subject}.md`.
+- Commit message pattern: `Review {TASK_ID}: {short subject}`.
+
+7. FOLLOW-UP
+- If review has actionable findings, run `SPECS/COMMANDS/PRIMITIVES/FOLLOW_UP.md`.
+- Add follow-up tasks to `SPECS/Workplan.md`.
+- Commit message pattern: `Follow-up {TASK_ID}: {short subject}`.
+- If no actionable findings, explicitly note FOLLOW-UP skipped.
+
+8. ARCHIVE-REVIEW
+- Move `REVIEW_{subject}.md` to `SPECS/ARCHIVE/_Historical/` or relevant task folder.
+- Update `SPECS/ARCHIVE/INDEX.md`.
+- Commit message pattern: `Archive REVIEW_{subject} report`.
+
+## Completion Criteria
+
+Consider the run complete only when all are true:
+- FLOW step sequence has been fully executed (or optional FOLLOW-UP formally skipped due to no findings).
+- Required artifacts exist in `SPECS/INPROGRESS/` and/or `SPECS/ARCHIVE/`.
+- Required quality gates were run and outcomes captured.
+- Commit checkpoints align with FLOW message patterns.
+
+## Trigger Phrases
+
+Use this skill when requests look like:
+- "Do the next task from start to end."
+- "Run the full FLOW workflow for the next task."
+- "Take this task all the way through branch, plan, execute, archive, and review."
+- "Strictly follow the instructions in the @SPECS/COMMANDS/FLOW.md file carefully for the next task. Do not stop between steps. Complete each phase of the FLOW process one by one without asking questions or pausing."

.agents/skills/flow-run/agents/openai.yaml

@@ -0,0 +1,4 @@
+interface:
+  display_name: "Flow Run"
+  short_description: "Run full FLOW command workflow end-to-end"
+  default_prompt: "Use $flow-run: Strictly follow the instructions in @SPECS/COMMANDS/FLOW.md for the next task, do not stop between steps, and complete each FLOW phase one by one without pausing."