skills/dbx-software-plan-first-implement-feature/SKILL.md
Manual trigger only. Use only when the user explicitly names `dbx-software-plan-first-implement-feature`, `$dbx-software-plan-first-implement-feature`, or asks to manually trigger this exact DBX Software Plan-First review-gated single-task implementation phase. Do not auto-trigger for ordinary implementation, tasks.md, next-task, or plan-first requests.
npx skillsauth add dbvc/skills dbx-software-plan-first-implement-featureInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
dbx- prefix for stable skills; use the prefixed skill names in handoffs and cross-skill routing.dbx-software-plan-first-implement-feature, $dbx-software-plan-first-implement-feature, or says to use/trigger this exact skill.用于按计划执行单个 task。
tasks.md 中第一个未完成 task。review-ready,用户 review 通过后运行 complete。references/workflow-rules.mdreferences/implement-notes.mdreferences/worktree-safety.mdreferences/review-checks.mdreferences/feedback-and-proof.mdreferences/impact-profiles.mdgit status --short --branch -uall
scripts/issue-workflow.sh status <issue-id>
scripts/issue-workflow.sh next <issue-id>
scripts/issue-workflow.sh review-ready <issue-id>
review-ready 摘要,等待用户 review。scripts/issue-workflow.sh complete <issue-id>
tasks.md 完成状态。使用中文 review-ready 或 complete 摘要。
development
Evidence-grounded technical implementation planning before code changes. Use when the user asks to plan a software feature, refactor, migration, bug-fix strategy, infrastructure change, validation strategy, rollout, or codebase modification before implementation. Produces a scoped plan contract with goal, non-goals, evidence boundary, source of truth, invariants, implementation slices, validation model, risks, and handoff. Do not use for direct implementation, concrete diff review, strict critique of an existing plan, product/design judgment, generic brainstorming, commit/PR writing, or the stateful dbx-software-plan-first phase chain unless explicitly requested.
development
Codex 专用的 subagent 上下文策略辅助技能。Use when 用户要求使用 Codex subagent delegation、Codex worker/explorer delegation、并行 review、独立 reviewer、隔离上下文、不要带上下文、fork_context=false,或把 review/dbx-linus-review/waza-check/plan-eng-review 等技能交给 Codex subagent 执行时。默认新开 Codex subagent 不继承父线程历史,只传最小任务摘要;只有用户明确要求继承父线程时才使用 fork_context=true。不要因为用户讨论业务代码里的 worker、browser worker、架构 explorer 概念而触发。
development
Use when the user asks to judge whether a product, feature, PRD, information architecture, content, interaction, UI flow, live product, implementation, roadmap, or competitor position is right, good, usable, valuable, coherent, worth building, or product-ready. Grounds judgment in target user, job/context, evidence, alternatives, critical path, trust, and implementation alignment. Ask blocking questions or collect evidence before judging when background is missing. Do not use for pure implementation, generic UI inspiration, ordinary code review without product judgment, generic market summaries, or unsupported guesses.
development
High-signal code change review workflow for PRs, patches, staged/index changes, working-tree diffs, commit ranges, and file-scoped review. Use when the user asks to review concrete code changes for functional/user-impact risks, data model correctness, state ownership, compatibility, or maintainability. Handles partial staged hunks and user-selected files/commits by selecting the exact review target before reading the diff. Do not use for implementation-only requests, generic code explanation, release publishing, issue triage, or plan-only Linus-style strict-pragmatic critique; for strict critique of a concrete diff, use this skill only to establish the target before dbx-linus-review.