salesforce-claude-framework: Command for Claude Code

.claude/commands/dev-docs.md

dev-docs is a command for Claude Code from ehebert7/salesforce-claude-framework. It costs 0 tokens per session (91 once invoked), scanned A, original, MIT.

A command that creates detailed development notes for the current coding task from prepared templates.

In plain words
What is it for?
It creates a task folder, copies the plan, context, and task templates, fills in their sections, and confirms creation.
Why use it?
It gives a task an agreed plan, context record, and checklist instead of leaving the work undocumented.

Command for Claude Code

Written for Claude Code: installed under .claude/.

This is ehebert7/salesforce-claude-framework's own configuration. It tells Claude Code how to work on salesforce-claude-framework itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything salesforce-claude-framework configures →

Reuse

Borrowing it

Nothing to install: this file belongs to ehebert7/salesforce-claude-framework. 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/ehebert7/salesforce-claude-framework/master/.claude/commands/dev-docs.md
Clone the repo
git clone --depth 1 https://github.com/ehebert7/salesforce-claude-framework

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.

agentmods badge for dev-docs

README.md
[![agentmods](https://agentmods.dev/badge/commands/ehebert7/salesforce-claude-framework/dev-docs/github.svg)](https://agentmods.dev/commands/ehebert7/salesforce-claude-framework/dev-docs)
Your own site
<a href="https://agentmods.dev/commands/ehebert7/salesforce-claude-framework/dev-docs"><img src="https://agentmods.dev/badge/commands/ehebert7/salesforce-claude-framework/dev-docs/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.

agentmods 80×15 button for dev-docs

Your own site · 80×15
<a href="https://agentmods.dev/commands/ehebert7/salesforce-claude-framework/dev-docs"><img src="https://agentmods.dev/badge/commands/ehebert7/salesforce-claude-framework/dev-docs.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 91 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.00091
Opus 5.5 $0.00000 $0.00036
Sonnet 5.5 $0.00000 $0.00018
Haiku 4.5 $0.00000 $0.00009

Measured 2mo ago against content hash 2807353f6187, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

dev-docs 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 2mo 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.

.claude/commands/dev-docs.md · 10 lines

What it actually says

Create comprehensive dev docs for the current task:

  1. Create directory: dev/active/[task-name]/
  2. Copy and populate templates:
    • [task-name]-plan.md from plan-template.md
    • [task-name]-context.md from context-template.md
    • [task-name]-tasks.md from tasks-template.md
  3. Fill in all sections based on the approved plan
  4. Confirm creation to user
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.

  1. 2mo ago First seen · 10 lines · 0 tokens per session scan A 2807353f6187

Subscribe to this mod's changes

dev-docs is a command published in the GitHub repository ehebert7/salesforce-claude-framework (12 stars, last pushed 11mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 91 tokens. 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-30.

Related

Other commands, from other repositories

API_REFERENCE

Generated from commands/specs/.json. Do not edit this file directly.

PranavNagrecha/AwesomeSalesforceSkills · 0 tokens

build-skills

End-to-end orchestrator that takes a count + optional topic hints and ships N production-grade skills with measurement-driven quality gates at every step.

PranavNagrecha/AwesomeSalesforceSkills · 0 tokens

onboard-source

One entrypoint for turning outside knowledge into catalog-quality skills.

PranavNagrecha/AwesomeSalesforceSkills · 0 tokens

clarify-requirements

Wraps agents/requirements-clarifier/AGENT.md. Takes one requirement — a paragraph, a worksheet, a backlog extract — searches local coverage for every capability it implies, harvests every row of every matching skill's ## Questions to Ask Before Configuring table, dedupes by meaning, proposes a default per question…

PranavNagrecha/AwesomeSalesforceSkills · 0 tokens

plan-build

Wraps agents/build-planner/AGENT.md. Takes a build directory whose plan.json is past gate G1 and writes the plan the rest of the loop executes: scope in and out, a fit-gap entry per capability, a decision per technology choice with the decision-tree branch that produced it, two to six milestones, and the ordered steps…

PranavNagrecha/AwesomeSalesforceSkills · 0 tokens

verify-plan

Wraps agents/plan-verifier/AGENT.md. For every step in plan.json it runs three independent adversarial lenses — executability (can the named agent actually produce these outputs from these inputs, and is it eligible to own the step in this buildmode?), grounding (do the cited skills, templates and decision-tree…

PranavNagrecha/AwesomeSalesforceSkills · 0 tokens