菜单
Convert repo-owned strategic ideas into a timestamped, execution-ready backlog plan using the active repo profile.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | backlog-plan |
| description | Convert repo-owned strategic ideas into a timestamped, execution-ready backlog plan using the active repo profile. |
| disable-model-invocation | true |
This is a local discovery wrapper for the shared Factory skill at factory/skills/backlog-plan/SKILL.md.
Before using this skill:
factory/skills/backlog-plan/SKILL.md exists.git submodule update --init factory
Then read factory/skills/backlog-plan/SKILL.md and follow that Factory skill using the active wrkr repo profile unless the user provides another explicit profile.
Project wrapper policy:
backlog_plan.output_dir, currently product/plans/backlog.product/plans/adhoc; that directory is reserved for one-off adhoc plans.Do not treat this wrapper as the source of truth for plan content. The Factory skill is authoritative for the generated plan structure.
Convert user-provided recommendations into a timestamped, execution-ready backlog plan using the active repo profile. Use when a repo needs a one-off plan that should not overwrite PLAN_NEXT.
Verify implemented Factory plans against original source requirements, run all required validation lanes, create a repair branch when gaps exist, and fix gaps until all requirements are satisfied.
Implement any valid Factory execution plan story-by-story using the active repo profile, planned changelog/versioning fields, and required validation lanes.
Run a profile-driven evidence-based OSS/product readiness audit across product model, onboarding, architecture, DX, security, release readiness, and market wedge.
Delete non-default local and configured-remote branches one-by-one using the active repo profile, safety checks, and a final prune/report.
Perform a profile-driven full-repository or scoped code review with severity-ranked findings focused on contracts, boundaries, fail-closed safety, determinism, portability, release integrity, and docs correctness.