Borrowing it
Nothing to install: this file belongs to PackmindHub/packmind. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/PackmindHub/packmind/main/.claude/skills/agentic-feature-framing/SKILL.mdgit clone --depth 1 https://github.com/PackmindHub/packmindWrote 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.
[](https://agentmods.dev/skills/packmindhub/packmind/agentic-feature-framing)<a href="https://agentmods.dev/skills/packmindhub/packmind/agentic-feature-framing"><img src="https://agentmods.dev/badge/skills/packmindhub/packmind/agentic-feature-framing/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.
<a href="https://agentmods.dev/skills/packmindhub/packmind/agentic-feature-framing"><img src="https://agentmods.dev/badge/skills/packmindhub/packmind/agentic-feature-framing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00134 | $0.01265 |
| Opus 5.5 | $0.00054 | $0.00506 |
| Sonnet 5.5 | $0.00027 | $0.00253 |
| Haiku 4.5 | $0.00013 | $0.00127 |
Grade A, and why
agentic-feature-framing 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 1mo 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.
How it starts
The opening of the file, as written. The whole thing — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Feature framing
You are settling what is being built. Not how. The output is one file:
.claude/features/<slug>/charter.md, from .claude/pipeline/charter.template.md.
Why this exists
Two reasons, and the second is the one that gets forgotten.
Scope and criteria are the escalation ladder. Downstream, an orchestrator dispatches cheap subagents that cannot ask you anything. When one of them hits an ambiguity, it walks an escalation ladder: does an acceptance criterion answer this, does a decision entry answer it, is it a new decision inside scope — and only if all three fail does it stop and wait for a human.
Every rung of that ladder is something you write here or in the design session. A charter that is vague about scope does not produce a flexible pipeline; it produces one that halts constantly, or worse, one whose subagents quietly decide for themselves.
And this phase, with 1b, is how the size of the work becomes visible. Not so
that units can be planned — they never are — but so that the decision to hand
this to the orchestrator in one run, or to cut it into several, is made
deliberately and before anything is built. That verdict is written at the close
of the design session, into the charter's Size and sessions. What you owe it
here is a coarser read: whether this is one feature at all.
Hard rules
- Write no code. Not an example, not a sketch, not a type definition.
- Edit no file but the charter.
- Do not design. "We could use a queue for this" is a decision-session question. If the user offers implementation, write down the requirement it implies and move on.
- Do not accept the first plausible framing. The first answer to "what are we building" is almost always the solution the user already has in mind, not the problem.
How to run the conversation
Start with the problem, and stay there longer than feels natural. Who hits this today, how often, what do they do instead. You are looking for the sentence that makes the acceptance criteria obvious.
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.
- 1mo ago First seen · 105 lines · 134 tokens per session scan A 19ff0a9ee5f2
agentic-feature-framing is a skill published in the GitHub repository PackmindHub/packmind (319 stars, last pushed 4d ago), licensed Apache-2.0. It adds 134 tokens to every session and 1,265 once invoked, about $0.0005 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-09-17.
Other skills, from other repositories
ce-compound
Document a recently solved problem or durable project vocabulary in docs/solutions/ or CONCEPTS.md. Use when capturing a learning after work.
ce-work
Execute a plan or concrete work prompt end-to-end. Use when implementing from docs/plans, a spec path, or a clear build request; use ce-debug for open-ended bugs.
sdd
Execute the Liatrio Spec-Driven Development (SDD) workflow when explicitly invoked by the user. NOTE: this skill is NOT intended to be dynamically loaded or automatically triggered; it should only ever be explicitly called by the user.
loadout-import-workflow
Import another repo's command/skill suite into loadout as a workflow. Use when the user points at an agent framework, plugin, or command pack (e.g. a GitHub repo, a .claude/commands/ directory, a skills pack) and wants its process turned into a loadout [[workflows]] entry — "import this workflow", "turn this plugin…
ce-commit-push-pr
Commit, push, and open a PR. Use when asked to ship/open a PR, or for PR-description-only flows like writing, rewriting, or describing a PR body.
loadout-migrate
Migrate existing global AI agent instructions into loadout. Use when adopting loadout, importing a CLAUDE.md / AGENTS.md / global agent rules into loadout, setting up /.config/loadout/config.toml, or turning prose agent instructions into reusable fragments and stack-targeted profiles.