Initial commit: add SB-Workflow skill and reference sources
This commit is contained in:
commit
77def46c5f
47 files changed
+2018
No files matched your search
@@ -0,0 +1,58 @@
|
||||
# One task record
|
||||
|
||||
Use one record for multi-step, multi-stage, or long-running work; short changes can use a brief plan and conversation. Read on creation/resumption, not every turn.
|
||||
|
||||
## Location and authority
|
||||
|
||||
Reuse the project's task-document convention. Otherwise use .tasks/<task-slug>.md under the project root. Avoid collisions and overwrites; ask about ambiguous task identity rather than selecting by modification time.
|
||||
|
||||
The effective protocol plan/version and hierarchical TODO in this record are the implementation specification and progress source. Keep goals, decisions, authorization, and evidence together. Do not create parallel full plans, decision logs, terminology files, or reports without a project convention or user need.
|
||||
|
||||
## Minimal structure
|
||||
|
||||
Write user-facing records in Chinese. Include only relevant sections; omit inapplicable fields. System usernames, Git branches, and per-step timestamps are not required.
|
||||
|
||||
~~~markdown
|
||||
# 任务名称
|
||||
|
||||
## 当前状态
|
||||
- 协议阶段与子阶段:
|
||||
- 有效计划版本与批准状态:
|
||||
- 批准依据及授权范围:
|
||||
- 当前 TODO 编号:
|
||||
- 阻塞、恢复条件与下一步:
|
||||
|
||||
## 目标、范围与验收
|
||||
|
||||
## 研究依据与未验证假设
|
||||
|
||||
## 决策与取舍
|
||||
|
||||
## 有效计划与分层 TODO
|
||||
|
||||
## 验证证据
|
||||
|
||||
## 修订与偏差记录
|
||||
|
||||
## 剩余风险与交付结论
|
||||
~~~
|
||||
|
||||
Use [todo.md](todo.md) for task IDs, nesting, states, verification, and parent completion. Give consequential decisions stable IDs when useful. Record question, choice, evidence, reason, accepted cost, and downstream effects. Deferred nonblockers need a revisit trigger; accepted risk is separate from settlement.
|
||||
|
||||
For UI/UX, keep the brief and approval, reference-research authorization, explicit candidate count, artifact scope, direction differences, selection, refinements, and rendering/interaction evidence here. Keep prototype approval separate from production approval. Record preview command, directory, port/URL, actual session/PID and ownership evidence, then verified cleanup.
|
||||
|
||||
## Update, revision, and migration
|
||||
|
||||
- Update current status, progress, factual corrections, and open items for readability.
|
||||
- Record actual approved version/content and authorization; never invent or expand it on resumption.
|
||||
- Preserve approved original decisions or sufficient exact content to reconstruct them. Append substantive revisions with affected IDs, original/replacement, reason, impact, supersession, and approval.
|
||||
- A revision does not inherit approval automatically; reconfirm affected parts, retaining unaffected decisions.
|
||||
- Record real commands, results, and scope. When applicable include baseline/after comparison, defect trigger and causal evidence, user-path results, protected behavior, bounded-experiment limits, and actual-artifact checks. Reuse existing sections rather than adding mandatory parallel reports. Preserve old results but mark affected TODOs 待验证 when later edits invalidate them.
|
||||
- Research, Grill, planning, and review may maintain records when permitted, not business code/configuration. If writing is unavailable, retain Chinese conclusions in conversation, mark persistence pending, and sync when allowed; do not request a host mode merely to save notes.
|
||||
- Import an existing host plan by retaining its original reference and approval history and reconciling verifiable effective content into this record. Do not keep two competing authoritative plans. Missing content or unclear approval remains an explicit gap; require no host tool merely to migrate.
|
||||
|
||||
## Resume and close
|
||||
|
||||
Read stage/sub-stage, effective version, approval, current/remaining IDs, evidence, and recent revisions. Reconcile actual files, dependencies, check freshness, and any recorded preview handles. Investigate discrepancies, protect unrelated changes, and establish the next action before continuing.
|
||||
|
||||
Close against acceptance with complete, partial, or blocked status and actual evidence. Keep failed/unrun checks, cleanup gaps, and remaining IDs visible. A final response is not evidence that the work is complete.
|
||||
Reference in new issue
Block a user