agentmods.dev

feature-spec

feature-spec is a skill for Claude Code, Codex from pproenca/dot-skills. It costs 55 tokens per session (1,003 once invoked), scanned A, original, MIT.

A planning guide for software features, including requirements, scope, priorities, acceptance criteria, technical details, and stakeholder decisions.

In plain words
What is it for?
It is for writing product requirements, defining user stories, prioritizing work, handling change requests, and aligning engineers, product managers, and other stakeholders.
Why use it?
It helps turn vague requests into an agreed plan and reduces uncontrolled scope changes during development.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

not rated 205repo +4 24d ago A scan Socket: passSnyk: passSkillSpector: pass 55 tokens original MIT

Good fit It is for writing product requirements, defining user stories, prioritizing work, handling change requests, and aligning engineers, product managers, and other stakeholders.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/pproenca/dot-skills/feature-spec
View source ↗ pproenca/dot-skills
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 pproenca/dot-skills --skill feature-spec
Clone the repo
git clone --depth 1 https://github.com/pproenca/dot-skills

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.

agentmods badge for feature-spec

README.md
[![agentmods](https://agentmods.dev/badge/skills/pproenca/dot-skills/feature-spec/github.svg)](https://agentmods.dev/skills/pproenca/dot-skills/feature-spec)
Your own site
<a href="https://agentmods.dev/skills/pproenca/dot-skills/feature-spec"><img src="https://agentmods.dev/badge/skills/pproenca/dot-skills/feature-spec/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 feature-spec

Your own site · 80×15
<a href="https://agentmods.dev/skills/pproenca/dot-skills/feature-spec"><img src="https://agentmods.dev/badge/skills/pproenca/dot-skills/feature-spec.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 55 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,003 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. Third-party audits
  • Socket pass 18 May 2026
  • Snyk pass 18 May 2026
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.00055 $0.01003
Opus 5 $0.00028 $0.00502
Sonnet 5 $0.00011 $0.00201
Haiku 4.5 $0.00006 $0.00100

Measured 6d ago against content hash 0e9aba99d4b1, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

feature-spec 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 6d 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/.experimental/feature-spec/SKILL.md · 100 lines

How it starts

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

Software Engineering Feature Specification and Planning Best Practices

Comprehensive feature specification and planning guide for software engineers, product managers, and technical leads. Contains 42 rules across 8 categories, prioritized by impact to prevent scope creep and ensure project success.

When to Apply

Reference these guidelines when:

  • Writing PRDs or feature specifications
  • Defining requirements or user stories
  • Managing scope and preventing scope creep
  • Prioritizing features and backlog items
  • Handling change requests
  • Aligning stakeholders on project goals

Rule Categories by Priority

Priority Category Impact Prefix
1 Scope Definition CRITICAL scope-
2 Requirements Clarity CRITICAL req-
3 Prioritization Frameworks HIGH prio-
4 Acceptance Criteria HIGH accept-
5 Stakeholder Alignment MEDIUM-HIGH stake-
6 Technical Specification MEDIUM tech-
7 Change Management MEDIUM change-
8 Documentation Standards LOW doc-

Quick Reference

1. Scope Definition (CRITICAL)

  • scope-define-boundaries - Define explicit scope boundaries
  • scope-document-assumptions - Document all assumptions explicitly
  • scope-work-breakdown - Break scope into measurable work items
  • scope-define-mvp - Define MVP before full feature set
  • scope-stakeholder-signoff - Get stakeholder signoff on scope

2. Requirements Clarity (CRITICAL)

  • req-specific-measurable - Write specific, measurable requirements
  • req-user-stories - Structure requirements as user stories
  • req-avoid-solution-language - Avoid solution-specific language
  • req-functional-nonfunctional - Separate functional and non-functional
  • req-consistent-terminology - Use consistent terminology
  • req-traceability - Maintain requirements traceability

3. Prioritization Frameworks (HIGH)

  • prio-moscow-method - Use MoSCoW prioritization method
  • prio-rice-scoring - Apply RICE scoring for objectivity
  • prio-value-vs-effort - Map value vs effort explicitly
  • prio-dependencies-first - Identify and order dependencies
  • prio-kano-model - Apply Kano model for feature classification

Read the full file on GitHub · 100 lines

Files

What ships with it

47 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.

  1. 6d ago First seen · 100 lines · 55 tokens per session scan A 0e9aba99d4b1

Subscribe to this mod's changes

feature-spec is a skill published in the GitHub repository pproenca/dot-skills (205 stars, last pushed 24d ago), licensed MIT. It adds 55 tokens to every session and 1,003 once invoked, about $0.0003 per session on Opus 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-03.

PlanningProject management
Related

Other skills, from other repositories

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

atmos-config

Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.

cloudposse/atmos · 31 tokens

story-readiness

Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…

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

autotask-creator

Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.

Orkas-AI/Orkas · 5 tokens

projects

List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.

me2resh/apexyard · 24 tokens