A project workflow guide for coordinating software work from status checks through planning, implementation, testing, integration, and review. It is tailored to the M3E project and assigns work between a director and Codex.

Use it to start development sessions, inspect current work, break tasks into deliverables, route work by role, run verification, update project records, and integrate completed changes.

It provides a repeatable way to select small tasks, track dependencies, verify changes, and record progress. It also clarifies which project files and branches should be used.

How akaghef/M3E configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to akaghef/M3E. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/akaghef/M3E/main/.claude/skills/devM3E/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/akaghef/M3E

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/akaghef/m3e/devm3e/github.svg)](https://agentmods.dev/skills/akaghef/m3e/devm3e)

Your own site

<a href="https://agentmods.dev/skills/akaghef/m3e/devm3e"><img src="https://agentmods.dev/badge/skills/akaghef/m3e/devm3e/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/akaghef/m3e/devm3e"><img src="https://agentmods.dev/badge/skills/akaghef/m3e/devm3e.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 226 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 3,609 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00226	$0.03609
Opus 5.5	$0.00090	$0.01444
Sonnet 5.5	$0.00045	$0.00722
Haiku 4.5	$0.00023	$0.00361

Measured 5d ago against content hash 27b4daf18fb0, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

devM3E scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 5d ago.

The scan reads SKILL.md. This mod also ships 2 executable files (scripts/aggregate_results.py, scripts/session_bootstrap.sh), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/skills/devM3E/SKILL.md · 304 lines

How it starts

The opening of the file, as written. The whole thing — 304 lines — stays where its author put it; the contents beside it link to each section on GitHub.

devM3E — M3E Development Orchestrator

M3Eプロジェクトの開発サイクルを回すオーケストレーションスキル。 skill-creatorの「intent capture → draft → test → eval → iterate」ループをソフトウェア開発に適用する。

Core Loop

1. Assess   — 現在地の把握（status, todo pool, daily, blocked items）
2. Plan     — タスク選定と分解（smallest deliverable first）
3. Execute  — 実装（サブエージェント分業 or インライン）
4. Verify   — 検証（テスト、ビルド、手動確認）
5. Integrate — 統合と記録（commit, daily更新, status更新）
6. Review   — ユーザーレビュー → フィードバック → 次サイクルへ

Phase 1: Assess（現在地の把握）

セッション開始時、まず以下を読む:

ファイル	目的
`docs/00_Home/Current_Status.md`	現在のスナップショット
`docs/06_Operations/Todo_Pool.md`	未着手タスクプール
`docs/daily/` 直近3日分	最近の作業経緯
`docs/tasks/todo_by_role.md`	ロール別タスク一覧

出力: 現在地サマリーを3行以内でユーザーに提示。blockedやriskがあれば先に伝える。

Phase 2: Plan（タスク選定と分解）

タスク選定基準

blocked解消が最優先
次にTodo Poolのstate=readyかつ優先度の高いもの
ユーザーが指定したタスク

タスク分解

タスクをTodoWriteで管理する。各タスクは:

1つの検証可能な成果物を生む
30分以内で完了見込み
依存関係を明示

ロール判定

タスクの性質に応じてロールを判定する。ただし厳密な境界は設けない:

ロール	担当領域	ブランチ
visual	UI・レンダリング・CSS・SVG	dev-visual
data	model・controller・API・永続化	dev-data
統合	仕様策定・マージ・CI・文書管理	dev-beta

Coworkセッションでは統合ロールとして振る舞い、必要に応じてvisual/dataのサブタスクをサブエージェントに委任する。

Phase 3: Execute（実装）

サブエージェント分業パターン

skill-creatorのgrader/comparator/analyzerに倣い、以下のサブエージェントを定義する。各エージェントの詳細は agents/ 配下を参照。

エージェント	用途	詳細
implementer	コード実装	`agents/implementer.md`
verifier	テスト・ビルド・回帰チェック	`agents/verifier.md`
doc-updater	daily更新・Decision Pool追記	`agents/doc-updater.md`
reviewer	差分レビュー・spec整合チェック	`agents/reviewer.md`

並列実行ルール

独立したタスクはサブエージェントを並列起動する
依存があるタスクは直列で、前段の完了を待つ
サブエージェント起動時はワークツリー分離（isolation: "worktree"）を推奨

インライン実行

軽微な変更（1ファイル20行以内）はサブエージェントを使わずインラインで実行する。

実装時の制約

beta/ が開発対象。final/ は触らない
コミットメッセージは imperative形式
docs配下の設計文書は日本語で記述する（Documentation_Rules準拠）

Phase 4: Verify（検証）

検証ステップ（verifierエージェント or インライン）

Read the full file on GitHub · 304 lines

Files

What ships with it

11 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

5d ago First seen · 304 lines · 226 tokens per session scan A 27b4daf18fb0

Subscribe to this mod's changes

devM3E is a skill published in the GitHub repository akaghef/M3E (11 stars, last pushed 5d ago), licensed MIT. It adds 226 tokens to every session and 3,609 once invoked, about $0.0009 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-10-02.

Planning Project management

story-readiness

Is a story implementation-ready? Checks clear acceptance criteria, open questions, ADR refs. READY/NEEDS WORK/BLOCKED/NOT ASSESSED.

Donchitos/Claude-Code-Game-Studios · 35 tokens

recipe-create-meet-space

Create a Google Meet meeting space and share the join link.

googleworkspace/cli · 18 tokens

workthreads

SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…

specstoryai/getspecstory · 126 tokens

M3E: Skill for Claude Code