What is feat-feature?

A workflow for planning a complete feature across backend, frontend, tests, and relevant documentation before code is written. It uses a structured set of questions and records the result as an action plan.

Use it for full-stack features such as a user CRUD feature, where CRUD means creating, reading, updating, and deleting records.

It makes business rules, acceptance checks, implementation order, and verification steps explicit before development starts. This reduces gaps between data work, server behavior, UI work, and tests.

feat-feature — Skill for Claude Code and Codex by pwdev-solucoes

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 pwdev-solucoes/pwdev-claude-marketplace --skill feat-feature

Clone the repo

git clone --depth 1 https://github.com/pwdev-solucoes/pwdev-claude-marketplace

Made for: Claude Code, Codex.

Or install pwdev-feat, the plugin that ships this one along with the rest of its 13 skills, 8 commands.

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/pwdev-solucoes/pwdev-claude-marketplace/feat-feature/github.svg)](https://agentmods.dev/skills/pwdev-solucoes/pwdev-claude-marketplace/feat-feature)

Your own site

<a href="https://agentmods.dev/skills/pwdev-solucoes/pwdev-claude-marketplace/feat-feature"><img src="https://agentmods.dev/badge/skills/pwdev-solucoes/pwdev-claude-marketplace/feat-feature/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/pwdev-solucoes/pwdev-claude-marketplace/feat-feature"><img src="https://agentmods.dev/badge/skills/pwdev-solucoes/pwdev-claude-marketplace/feat-feature.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 621 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.00131	$0.00621
Opus 5.5	$0.00052	$0.00248
Sonnet 5.5	$0.00026	$0.00124
Haiku 4.5	$0.00013	$0.00062

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

Security

Grade A, and why

feat-feature 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 27d 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.

plugins/pwdev-feat/skills/feat-feature/SKILL.md · 44 lines

What it actually says

Feature plan

Plan type feature — full scope: backend, frontend, tests and documentation as applicable, split into clearly ordered Execution Steps. You run in the MAIN session: you interview the human, so never delegate this skill to a subagent.

Procedure

Language — resolve lang (references/language.md).
Method — follow references/pwdevia-method.md end to end: read context (project instructions file, .planning/feat/codebase.md, all four .planning/feat/context/*.md, map staleness, memory), interview (max 2 rounds), answer the 7 questions, render templates/plan.md with plan_type: feature, lint it, present the summary.
Focus for this type
- Persona: full-stack engineer on the project's real stack (from the context documents).
- Order the steps: data/migrations → domain/services → API → UI → tests → docs.
- Every business rule becomes at least one AC-*; every AC has a verification.
- With UI (**UI:** yes): include the E2E scenario files (<tests-dir>/e2e/scenarios/E2E-nnn-*.scenario.json) and their exported specs (<tests-dir>/e2e/generated/E2E-nnn-*.spec.ts) in §4 and playwright-cli checks in §5 — references/testing.md.
- Consider validation, error handling, authorization and migrations explicitly.

Prohibitions

Never write code — only the plan.
Never skip any of the 7 questions or leave an AC without verification.
Never create a plan with more than 10 steps — split into several plans.

Language: resolve lang per references/language.md before any human-facing output. Safety: never read or expose .env* (except .env.example/.template/.sample), keys, certificates or credentials — references/safety.md. Paths references/, scripts/, templates/, schemas/ are relative to the plugin root (references/runtime.md).

Files

What ships with it

1 file 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.

agents/openai.yaml 179 B

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.

27d ago First seen · 44 lines · 131 tokens per session scan A dc3fdc7171e6

Subscribe to this mod's changes

feat-feature is a skill published in the GitHub repository pwdev-solucoes/pwdev-claude-marketplace (3 stars, last pushed 10d ago), licensed Apache-2.0. It adds 131 tokens to every session and 621 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-28.

Planning Testing

research-engineer

An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.

davila7/claude-code-templates · 43 tokens

tika-eval-compare

Compare extracts from two Tika builds over a corpus to detect regressions in content, encoding, exceptions, and embedded-document handling. Use for "compare before/after extracts", "eval this change against the corpus".

apache/tika · 50 tokens

cua-driver

Use Cua Driver for desktop or browser tasks that are awkward or unavailable through Bash/APIs, or when the user explicitly wants GUI interaction: app testing, visual bug reproduction, form filling, calendar entry, screenshots, and demo recording. Also covers Cua setup; not OpenAI Codex Computer Use or web research.

davidondrej/skills · 68 tokens

feat-feature