build-plan

Imported from fareedst/bkpdir (.cursor/skills/build-plan/SKILL.md). Install upstream with npx skills add fareedst/bkpdir --skill build-plan. Copyright stays with the author.

build-plan

Explicit invocation only (@build-plan or prompt-type: build-plan).

This skill is the workflow source of truth for client prompt-type invocation. copy_files.sh installs it under .cursor/skills/build-plan/. Task wrappers under .cursor/agents/ remain TIED-source development artifacts only. [REQ-PROMPT_TYPE_GLOBAL_SKILLS] [ARCH-PROMPT_TYPE_GLOBAL_SKILLS] [IMPL-PROMPT_TYPE_GLOBAL_SKILLS]

Inputs

• Optional prompt envelope: prompt-type: build-plan, git-condition: (informational)
• Linked plan: the attached or in-message approved plan to execute. Required.
• Invocation remainder: optional constraints; do not invent a plan from remainder alone.

TIED applicability

Full TIED execute — tied-boundary.md. Omits Refine.

Procedure

Execute the linked plan in this order:

1. Guiding vocab — guiding-vocab.md
2. Plan — tied-plan-citdp-build.md
3. Implement — tied-implement.md

Select profile_depth (minimal, integrated, or strict_candidate) and gate policy before depth-dependent inquiry. The linked Tracker and CITDP are inputs to every gate; do not substitute caller assertions for their evidence.

If neither a linked plan nor an in-message plan is present, stop.

Gates

• Before any completion or close-out claim, CALL sub-close-out-evidence-sync (sync dispositions, collect manifest, reconcile with include_process_grade, rebuild/validate envelope). Gate-only handoffs are incomplete at integrated depth — see completion-signals-handoff.md. Required flags: --envelope-blocking --sync-dispositions --reconcile on tools/bootstrap/templates/run-close-out-gates.mjs at verification-gate and close-out.
• Before implementation, call tied_checklist_gate_validate with phase: pre_implementation. Do not start code until it allows progression.
• At verification, call the same validator with phase: verification and pass its validated result to tied_verify. When depth_tier is integrated or strict_candidate, supply identity-bound activation evidence (prefer tied_checklist_activation_collect when phase artifact dirs exist).
• Before parent handoff, when depth_tier is integrated or strict_candidate, require verification gate allowed: true and document that close_out must call tied_checklist_gate_validate with activation (or a valid close-out inquiry waiver). If the gate returns allowed: false, label the work incomplete — do not claim success.
• Missing, malformed, stale, or unjustified process evidence blocks progression.

Outputs

Implementation per Tracker; CITDP record after behavior changes; verification gate. Parent handoff must include the three completion signals (machine / process / ledger) per completion-signals-handoff.md. Label close-out deferred when only the verification gate has run.

Forbidden

pbpaste/pbcopy, automatic git, unapproved repo inspection, Refine section.