A planning workflow that turns a feature specification into implementation design documents. It uses project rules and templates to produce research, data models, contracts, and setup guidance.

Use it after specifying a feature to create its implementation plan and supporting design artifacts.

It exposes unknowns and rule conflicts before coding, so implementation work has a clearer technical direction.

plan — Skill for Claude Code and Codex by akka/ai-marketplace

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add akka/ai-marketplace --skill plan

Clone the repo

git clone --depth 1 https://github.com/akka/ai-marketplace

Made for: Claude Code, Codex.

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/akka/ai-marketplace/plan/github.svg)](https://agentmods.dev/skills/akka/ai-marketplace/plan)

Your own site

<a href="https://agentmods.dev/skills/akka/ai-marketplace/plan"><img src="https://agentmods.dev/badge/skills/akka/ai-marketplace/plan/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/akka/ai-marketplace/plan"><img src="https://agentmods.dev/badge/skills/akka/ai-marketplace/plan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 1,269 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.00016	$0.01269
Opus 5.5	$0.00006	$0.00508
Sonnet 5.5	$0.00003	$0.00254
Haiku 4.5	$0.00002	$0.00127

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

Security

Grade A, and why

plan 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 9d ago.

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.

skills/plan/SKILL.md · 93 lines

How it starts

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

User Input

You MUST consider the user input before proceeding (if not empty).

Outline

Setup: Call the akka_sdd_list_specs MCP tool to find the target feature. Then call akka_sdd_get_template with template_name="plan" to get the plan template. Identify the feature's spec path (FEATURE_SPEC) and plan destination (FEATURE_DIR/plan.md).
Load context: Read FEATURE_SPEC and akka_sdd_constitution. If the spec contains unresolved [NEEDS CLARIFICATION] markers for policy decisions (thresholds, access permissions, retention, sensitive-data rules, approvals), report them, recommend /akka:clarify, and stop; do not decide them through research. Load IMPL_PLAN template (already copied).
Execute plan workflow: Follow the structure in IMPL_PLAN template to:
- Fill Technical Context (mark unknowns as "NEEDS CLARIFICATION")
- If the spec involves agents or model-generated behavior: check the project's installed Akka SDK version and its local documentation before choosing guardrail, classifier, sanitizer, evaluator, or identity mechanisms. Do not assume features newer than that version and do not upgrade the Akka SDK implicitly; if a required feature needs a newer version, record the upgrade as an explicit decision in research.md.
- Fill Constitution Check section from constitution
- Evaluate gates (ERROR if violations unjustified)
- Phase 0: Generate research.md (resolve all NEEDS CLARIFICATION)
- Phase 1: Map domain concepts to Akka components (Component Architecture table), then generate data-model.md, contracts/, quickstart.md
- Re-evaluate Constitution Check post-design
Stop and report: Command ends after Phase 2 planning. Report branch, IMPL_PLAN path, and generated artifacts.

Phases

Phase 0: Outline & Research

Extract unknowns from Technical Context above:
- For each NEEDS CLARIFICATION → research task
- For each dependency → best practices task
- For each integration → patterns task

Read the full file on GitHub · 93 lines

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.

9d ago Changed · +1 lines f0e3acfdcb40
1mo ago Changed · +7 lines 3f3c0dea9716
2mo ago First seen · 85 lines · 16 tokens per session scan A bf31c9e4ed67

Subscribe to this mod's changes

plan is a skill published in the GitHub repository akka/ai-marketplace (7 stars, last pushed yesterday), licensed Apache-2.0. It adds 16 tokens to every session and 1,269 once invoked, about $0.0001 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-08-31.

Claude Code Planning ai akka gemini-ai spec-driven-development

gsd-plan-review-convergence

Cross-AI plan convergence - replan until review concerns are resolved.

open-gsd/gsd-core · 21 tokens

gsd-audit-milestone

Audit milestone completion against original intent before archiving.

open-gsd/gsd-core · 17 tokens

gsd-ns-manage

Invoke this Pi skill with /skill:gsd-ns-manage.

open-gsd/gsd-core · 16 tokens

spec-kitty-charter-doctrine

Run charter interview, generation, context, and sync workflows for project governance in Spec Kitty 3.x. Access doctrine artifacts programmatically via DoctrineService. Resolve agent profiles. Load action-scoped governance context iteratively, not all at once. Triggers: "interview for charter", "generate charter"…

Priivacy-ai/spec-kitty · 135 tokens

dependency-upgrade

Plan, batch, and verify dependency upgrades safely. Triages outdated packages into risk tiers, upgrades in order (dev/minor/patch first, runtime majors last), verifies each batch, and produces an auditable commit sequence. Use when asked to "upgrade deps", "bump packages", "update nodemodules", "fix vulnerabilities"…

open-gsd/gsd-pi · 90 tokens

forensics

Post-mortem a failed GSD auto-mode run. Traces symptom to root cause via .gsd/ activity, journal, metrics, and lock artifacts, producing a filing-ready bug report with file:line refs and a fix suggestion. Use when asked to "forensics", "post-mortem", "why did auto-mode fail", "trace the stuck loop", "debug the crash"…

open-gsd/gsd-pi · 112 tokens