원클릭으로
spok-flow
end-to-end research → design → plan → implement → review → commit workflow for a single chunk. Driven by spok-apply.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
메뉴
end-to-end research → design → plan → implement → review → commit workflow for a single chunk. Driven by spok-apply.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Ship the next unchecked chunk from spok/changes/<name>/tasks.md end-to-end via the vendored spok-flow skill. Use when the user wants to implement the next chunk of a Spok change.
Archive a completed Spok change. Applies any delta specs to the main specs unconditionally, then moves the change directory under changes/archive/.
Commit Changes in CI with no user interaction
first step of planning
convert structure outline into a detailed implementation plan
generate research questions based on a task, spec, or ticket
| name | spok-flow |
| description | end-to-end research → design → plan → implement → review → commit workflow for a single chunk. Driven by spok-apply. |
| argument-hint | <task-dir> (absolute path to a pre-staged chunk directory containing ticket.md) |
| version | 0.3.0 |
spok-apply has already created the task directory and written ticket.md for the chunk to execute. The argument to this skill is the absolute path to that directory (e.g. spok/changes/<change-slug>/.flow/<chunk-slug>/).
Verify the directory exists and contains
ticket.mdusing the Read tool. Do NOT recreate the directory or overwriteticket.md.
If ticket.md is missing, halt and report back — spok-apply is responsible for staging it.
For each workflow step below, launch the named agent with the Agent tool and subagent_type: general-purpose.
Run steps sequentially in the foreground because each step depends on the previous step's returned path.
Launch lead-researcher-questions.
Call the
spok-create-research-questionsskill with the path to our ticket file as the argument using the Skill tool. When complete, return the absolute path of the research questions document that was created.
Launch lead-researcher. Pass the absolute path of the research questions document returned by step 1.
Call the
spok-create-researchskill with the path to our research questions document only as the argument using the Skill tool. When complete, return the absolute path of the research document that was created.
Launch lead-design-discussion.
Call the
spok-create-design-discussionskill with the path to our task directory as the argument using the Skill tool. When complete, return the absolute path of the design discussion document that was created.
Launch lead-structure-outline.
Call the
spok-create-structure-outlineskill with the path to our task directory as the argument using the Skill tool. When complete, return the absolute path of the structure outline document that was created.
Launch lead-plan.
Call the
spok-create-planskill with the path to our task directory as the argument using the Skill tool. When complete, return the absolute path of the plan document that was created.
Launch lead-implementer.
Call the
spok-implement-planskill with the path to our task directory as the argument using the Skill tool. When complete, return the summary of the implementation.
Launch lead-simplifier.
Call the
spok-simplifyskill using the Skill tool. When complete, return the summary of the simplification.
Launch lead-validator.
Call the
spok-validate-implementationskill with the path to our task directory as the argument using the Skill tool. When complete, return the validation summary and recommendations.
Launch lead-committer.
## Important guidelinesCall the
spok-ci-commitskill using the Skill tool. When complete, return the commit hashes and summary.