AgentSkillsCN

plan-ops

在本仓库中运行常见的规划工作流：持续规划、执行已批准的计划、更新计划文档并进行审计，最后通过提交/推送/PR 完成。当用户要求重复执行规划动作、循环执行计划，或在计划完成后自动进行审计与提交时，此技能将为您排忧解难。

SKILL.md
--- frontmatter
name: plan-ops
description: Run common planning workflows in this repo: keep planning, execute approved plan, refresh plan docs/audit, and finalize with commit/push/PR. Trigger when user asks for repeated planning actions, plan execution loops, or post-plan audit/commit automation.

Skill: plan-ops

Purpose

Provide a consistent command-style workflow for common planning actions without repo hooks.

Trigger Phrases

Use this skill when user messages include any of these intents:

  • •"keep planning"
  • •"review plan"
  • •"execute this plan <path>"
  • •"approve plan <path>"
  • •"refresh/update plan audit"
  • •"commit/push/open PR for plan work"

Commands the user can invoke

Treat these as direct workflow commands in chat.

  1. •plan:keep <path>
  • •Read the plan and continue refining it only (no code changes).
  • •Output updated decision-complete plan content.
  1. •plan:review <path>
  • •Review the plan quality and decision-completeness.
  • •Return concrete findings/gaps and required fixes before approval.
  1. •plan:execute <path>
  • •Execute plan end-to-end with normal repo workflow.
  • •Use TDD where applicable, run validations, summarize RED/GREEN evidence.
  1. •plan:audit
  • •Update docs/plans/plan-doneness-audit-2026-02-08.md to reflect current state.
  • •Ensure PR/branch status and implemented/planned classifications are consistent.
  1. •plan:finalize <message>
  • •Stage relevant plan/docs/code files.
  • •Commit with provided message.
  • •Push branch and open/edit PR when requested.
  1. •plan:approve <path>
  • •Approval workflow for your default sequence:
    1. •confirm plan is in docs/plans/planned/
    2. •commit the approved plan doc change(s) first
    3. •audit all plans by updating docs/plans/plan-doneness-audit-2026-02-08.md
    4. •commit the audit update
    5. •optionally push/open PR when requested

Repo Constraints

  • •Keep tests offline and deterministic.
  • •Use repo-local executables (.venv/bin/...).
  • •Do not touch data/, models/, notebooks/, betslips/ for planning flows.
  • •Keep changes surgical and scoped to the requested plan.

Validation Defaults

  • •Lint: .venv/bin/ruff check .
  • •Tests: .venv/bin/pytest -q
  • •For docs-only updates: skip full tests unless requested, but still run quick consistency checks (rg, git diff, status checks).

Notes

  • •This skill intentionally replaces hook-based automation with explicit chat commands.
  • •If the user asks for global Codex behavior changes, explain that repo-local skills cannot modify product-level UI hooks.