Steering - Workflow Management

VerifiedCaution

This skill creates a structured workflow by generating requirements, design, and tasklist files under .steering/ for each work instruction. It uses tasklist.md as the single source of truth for progress, operating in plan, implement, and reflect modes. Use it when you need to plan a task, track its implementation, or review completed work.

Sby Skills Guide Bot
ProductivityIntermediate
3/4/2026
Claude Code
#task-planning#progress-tracking#workflow#project-documentation#checklist

Recommended for

Automated summary

Creates a .steering/ folder per work item containing requirements.md, design.md and tasklist.md, then drives implementation using tasklist.md as the single source of truth for progress.

Strengths

  • Three explicit modes (plan / implement / reflect) that structure the whole work cycle
  • tasklist.md is updated after every completed task, preventing stale checklists
  • Requirements, design and tasklist templates are provided under references/templates
  • Out-of-scope work is explicitly pushed into a separate steering session

Limitations

  • The skill, its templates and formats are written in Japanese
  • Tracking quality depends on manually updating the tasklist; nothing is verified automatically
  • One rigid folder per session, which is overkill for tiny edits
When to use it

Use it when a feature or change needs written scoping, a task breakdown and progress tracking across multiple sessions.

When not to use it

Avoid it for a one-line fix or throwaway exploration where generating three planning files would be disproportionate.

Security analysis

Caution
Quality score85/100

The skill defines a legitimate planning/implementation/reflection workflow and only writes project-local steering files. No destructive commands, secret exfiltration, obfuscation, or safety-disabling instructions are present, but the broad Bash permission warrants ordinary caution.

Findings
  • •Bash is included in allowed-tools even though the workflow mainly needs file reads/writes and directory creation; no command-level restrictions are specified.
How this analysis is made

Examples

Plan a new feature
steering開始 — ユーザープロフィール編集機能の requirements / design / tasklist を .steering/ に作成して、タスクを具体的に分解して
Work through the tasklist
実装を進めて: .steering/20250601-user-profile の tasklist を先頭から消化し、1タスク完了するごとにチェックを付けて更新して
Record a retrospective
全タスクが完了したので reflect モードで振り返りを記録して、学びと改善点をまとめて

name: steering description: 作業指示ごとに .steering/ 配下へ requirements/design/tasklist を作成し、tasklist.md を唯一の進捗ソースとして実装を推進する。計画(作成)/実装(ループ)/振り返り(記録)の3モードで運用。「作業を計画して」「タスクリストを作成」「steering開始」「実装を進めて」などの依頼時に使用。 allowed-tools: Read, Write, Edit, Glob, Grep, Bash

Steering Skill

作業を計画・追跡・振り返りするためのワークフロー管理スキル。

目的

  • .steering/ に「今回の作業の要求・設計・タスク」を必ず残す
  • tasklist.md を進捗の唯一の正(Single Source of Truth)にする

参照ファイル

| ファイル | 読むタイミング | |----------|----------------| | references/guide.md | 詳細ルール | | references/templates/requirements.md | 要求テンプレート | | references/templates/design.md | 設計テンプレート | | references/templates/tasklist.md | タスクリストテンプレート |

入出力

  • 入力: ユーザーの指示(機能名/変更内容)、既存 docs(PRD/設計/アーキ等)
  • 出力:
    • .steering/<YYYYMMDD>-<slug>/requirements.md
    • .steering/<YYYYMMDD>-<slug>/design.md
    • .steering/<YYYYMMDD>-<slug>/tasklist.md

モード

1. plan モード

3ファイル作成 + tasklist具体化

2. implement モード

tasklist を先頭から消化し、都度更新(未完了を残さない)

3. reflect モード

tasklist の振り返り欄を更新(全タスク完了後のみ)

手順

plan モード

  1. 既存 docs を読んで方針を掴む
  2. ディレクトリを作成: .steering/<YYYYMMDD>-<slug>/
  3. テンプレから3ファイルを生成
  4. tasklist を具体的なタスクに分解

implement モード

  1. tasklist を読む
  2. 未完了タスクを1つ選ぶ
  3. 実装する
  4. tasklist を更新
  5. 1に戻る

reflect モード

  1. 全タスク完了を確認
  2. 振り返りを記録
  3. 学びや改善点をまとめる

tasklist.md 形式

# タスクリスト

## 概要
- 作業名: [作業名]
- 開始日: YYYY-MM-DD
- 状態: planning / in_progress / done

## タスク

- [ ] タスク1
- [ ] タスク2
- [x] 完了したタスク

## 振り返り

(全タスク完了後に記入)

注意事項

  • implement中はtasklistを頻繁に更新する
  • 1タスク完了ごとにチェックを付ける
  • 新しいタスクが発生したら追加する
  • スコープ外のタスクは別のsteeringセッションにする

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/steering-workflow-management-mmbizjki/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/steering-workflow-management-mmbizjki' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/steering-workflow-management-mmbizjki/download' --output '.skill-downloads/steering-workflow-management-mmbizjki/SKILL.md.part' && mv '.skill-downloads/steering-workflow-management-mmbizjki/SKILL.md.part' '.skill-downloads/steering-workflow-management-mmbizjki/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

Tools declared by the author (check availability in your agent): Read, Write, Edit, Glob, Grep, Bash

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.

Claude Code
test -f '.skill-downloads/steering-workflow-management-mmbizjki/SKILL.md' && test -s '.skill-downloads/steering-workflow-management-mmbizjki/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/steering' && cp -R '.skill-downloads/steering-workflow-management-mmbizjki' '.claude/skills/steering'

OpenSkills

OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.

Official OpenSkills installation
openskills install './.skill-downloads/steering-workflow-management-mmbizjki'

openskills read 'steering-workflow-management-mmbizjki'

Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.

For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.

openskills sync

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/steering-workflow-management-mmbizjki/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills