dbvc/dbx-software-plan-first-finalize-plan
skills/dbx-software-plan-first-finalize-plan/SKILL.md
Manual trigger only. Use only when the user explicitly names `dbx-software-plan-first-finalize-plan`, `$dbx-software-plan-first-finalize-plan`, or asks to manually trigger this exact DBX Software Plan-First plan finalization phase. Do not auto-trigger for ordinary plan writing, finalize, seal, or implementation requests.
$ install --global
skillsauthnpx skillsauth add dbvc/skills dbx-software-plan-first-finalize-planInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Jun 9, 2026, 2:34 AM121.8s20 files scanned
SKILL.md
- name:
- dbx-software-plan-first-finalize-plan
- description:
- Manual trigger only. Use only when the user explicitly names `dbx-software-plan-first-finalize-plan`, `$dbx-software-plan-first-finalize-plan`, or asks to manually trigger this exact DBX Software Plan-First plan finalization phase. Do not auto-trigger for ordinary plan writing, finalize, seal, or implementation requests.
DBX Software Plan-First Finalize Plan
DBX repository notes
- This repository uses the
dbx-prefix for stable skills; use the prefixed skill names in handoffs and cross-skill routing. - Keep this phase self-contained: load only the required references for the active phase, and do not pull sibling skill files unless the workflow explicitly hands off to that phase.
Manual Trigger
- Manual trigger only.
- Use only when the user explicitly names
dbx-software-plan-first-finalize-plan,$dbx-software-plan-first-finalize-plan, or says to use/trigger this exact skill. - Do not auto-trigger for ordinary plan writing,
plan.md/tasks.md, finalize, seal, or plan-first requests.
用于把已经收敛的计划写入过程产物，并建立 workflow seal。
语义
- 只能在 Goal、Scope、Approach、Validation、Plan Strategy、Impact Profile、Impact Boundary 已完整时使用。
- 如果需要仓库事实但尚未 grounding，先交给
dbx-software-plan-first-ground-plan。 - 如果计划会新增、移动或固定 source/config/test/doc 产物，产物归属必须已经由项目事实或用户确认支持；归属未定时不要 seal，先返回 grounding 或澄清。
- 写入中文
plan.md和tasks.md。 - 运行
scripts/issue-workflow.sh seal <issue-id>建立 seal。 - 计划过程产物固定写入
.plan-first/issues/<issue-id>/，不作为提交产物；若.plan-first/config.toml显式配置plan_docs.mode = "tracked"，只提交同步到项目文档路径的plan.md和tasks.md副本。 - 是否自动提交以及提交格式由
.plan-first/config.toml控制。
必须读取
references/workflow-rules.mdreferences/plan-template.mdreferences/tasks-template.mdreferences/config.mdreferences/impact-profiles.mdreferences/artifact-evidence-boundary.md
工作流
- 运行：
scripts/issue-workflow.sh init <issue-id>
- 用中文填写
plan.md和tasks.md。 - 确认
tasks.md每个任务包含：验收:、验证:，以及必要的使用检查:、依赖:、约束:。会新增或迁移产物的任务，必须在约束:中写明产物归属、依据和禁止误放的边界。 - 运行：
scripts/issue-workflow.sh seal <issue-id>
- 报告 workspace root、计划文件位置、配置模式、任务数量和下一步执行命令。
禁止事项
- 不在决策不完整时写计划。
- 不把项目特定规则写进通用 skill；只把本仓库 grounding 到的规则写进本 issue 计划。
- 不跳过 seal。
- 不在 finalize 阶段实现代码。
输出
用中文说明：workspace root、计划文件位置、任务数量、影响画像、验证模型、配置模式、下一步执行命令。
Related Skills
dbvc/dbx-technical-plan
development
VerifiedTrustedCommunity
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.
5SKILL.mdUpdated Jun 12, 2026
dbvc/dbx-subagent-context
development
VerifiedTrustedCommunity
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 概念而触发。
3SKILL.mdUpdated Jun 9, 2026
dbvc/dbx-product-judgment
development
VerifiedTrustedCommunity
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.
3SKILL.mdUpdated Jun 9, 2026
dbvc/dbx-diff-review
development
VerifiedTrustedCommunity
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.
3SKILL.mdUpdated Jun 9, 2026