菜单
Use when the user wants to mirror chevp-ai-framework plan files (context/plans/**/*.md) to GitHub Issues, or says "sync plans", "issue für §X.Y", "plans als issues anlegen", "create issues from plans", "spiegle backlog nach github". Wraps integration/github-issues/sync-plans-to-issues.py.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when an approved EXP plan is ready to be implemented and a Production-Plan (PRD) is needed, or when the user says "PRD plan", "production plan", "produce", "implement EXP-NNN", "draft PRD". Produces a PRD per the chevp-ai-framework template.
Use when an out-of-scope item, Challenger-identified failure mode, or NOT-in-Scope row warrants its own future plan (Rule 12). Trigger phrases: "create proposal", "PROP for this", "open a proposal", "log this for later", "this is out of scope but worth tracking". Produces a `PROP-NNN` file per the plan-proposal template.
Use before requesting G2 approval for an EXP plan, or when scope changes are proposed mid-Production (Rule 11 / Challenger role). Trigger phrases: "run challenger", "challenge this plan", "stress-test the approach", "draft the challenger block", "what could go wrong with this plan". Produces the four mandatory Challenger sections per [02-exploration/challenger.md].
Use when an Exploration cycle is wrapping up and the `insights.md` learning artifact is needed (mandatory before G2), or when Production has revealed implementation surprises that must be appended (Rule 9 / Learning Loop). Trigger phrases: "write insights", "insights file", "what did we learn", "log insights", "update insights with implementation surprises".
Use when the user wants to record an architecture decision, says "write an ADR", "new ADR", "document this decision", or when a non-trivial architectural choice is made during Context or Exploration that future contributors need to understand.
Use when the user starts a new task and a Context-Plan (CTX) is needed, or when they say "context plan", "CTX", "start context step", or a new request arrives with no active plan. Produces a CTX plan per the chevp-ai-framework template.
| name | sync-plan-issues |
| description | Use when the user wants to mirror chevp-ai-framework plan files (context/plans/**/*.md) to GitHub Issues, or says "sync plans", "issue für §X.Y", "plans als issues anlegen", "create issues from plans", "spiegle backlog nach github". Wraps integration/github-issues/sync-plans-to-issues.py. |
Mirrors plan files in context/plans/<phase>/ to GitHub Issues, one issue
per plan. Source-of-truth stays the markdown file; the issue body links
back to it. Idempotent — re-running skips existing issues.
.plan-sync.json at its root (see
../../integration/github-issues/.plan-sync.example.json).
If missing, stop and offer to create one based on the project's
CLAUDE.md and existing context/plans/ layout. Do not guess repo
or repo_url_prefix — ask.gh is authenticated against the target repo (gh auth status).id: (flat) or paragraph: (paragraph numbering), plus
type: and ideally title:.repo slug; default plan_dirs to ["context/plans/backlog", "context/plans/active"]).python3 path/to/chevp-ai-framework/integration/github-issues/sync-plans-to-issues.py --dry-run --limit 3
--limit) once the user
approves the dry-run output.--limit 1 after
temporarily reducing plan_dirs to the directory containing that
plan, OR fall back to a direct gh issue create with the same title
format the script would produce. Prefer the script for consistency.gh issue create and gh label create — both are
user-visible writes to GitHub. Always confirm intent before the first
non-dry-run invocation.--update without explicit user request — it overwrites
existing issue bodies.plan_dirs config rather than assuming success.