bf-task-fourpiece - SKILL.md Agent Skill

name: bf-task-fourpiece description: "Part of the Blueprintflow methodology. Use when a task.md exists, concrete task work is starting, and task baseline docs are missing."

Create the task baseline docs. Do not start implementation.

If using-plueprint is not active, STOP here. Load using-plueprint with the user's input; do nothing else in this skill until it routes back.

Use when all are true:

bf-milestone-breakdown produced reviewed task boundaries and the task is starting.
The task folder exists under docs/tasks/<phase>/<milestone>/<task>/.
task.md exists and was created by bf-milestone-breakdown.
The four-piece baseline docs do not exist or need repair before code starts.

Create or repair only these task baseline docs:

File	Owner	Required content
`spec.md`	Architect	Spec brief sections 0-4 only: constraints, segmentation, carry-over, reverse checks, out-of-scope
`stance.md`	PM	5-7 stances anchored to blueprint sections, with constraints and blacklist grep
`acceptance.md`	QA	Acceptance checks aligned 1:1 with spec segments
`content-lock.md`	PM	UI text/DOM literal locks, UI tasks only

Do not create design.md, implementation files, task PR state, worktree state, or merge/cleanup instructions in this skill.

Read task.md first.
Read the cited locked next-blueprint anchors.
Create spec.md from the task scope, anchors, out-of-scope, dependencies, and acceptance slice.
Create stance.md from the locked product stance and explicit anti-constraints.
Create acceptance.md aligned with spec.md segments.
Create content-lock.md only when the task changes UI copy or DOM literals.
Cross-check the four files against each other and against task.md.
Record the handoff: four-piece baseline ready; code-facing design is next.

Every four-piece file cites the relevant blueprint anchor or task contract section.
acceptance.md has one checkable outcome per spec segment.
stance.md names what the task is not allowed to become.
content-lock.md is absent or explicit; no empty placeholder file.
No file broadens the task.md scope.

Skipping one of the required baseline files.
Rewriting task.md inside this skill; send scope changes back to bf-milestone-breakdown for boundary repair.
Writing implementation design or code here.
Writing PR, worktree, branch, merge, or cleanup procedure here.
Treating a milestone as the task scope.

follow skill bf-task-fourpiece