What is feature-development?

A required workflow for adding features to a monorepo, which is a codebase containing several related apps. It requires a written specification, a generated starting structure, failing tests, and then the implementation.

Adding an endpoint, screen, or other capability to the API, web, mobile, desktop, or static parts of the project.

It prevents developers from inventing requirements, skipping tests, or creating feature folders in the wrong way. The fixed order keeps changes consistent across apps.

How LooseWireDev/mealforge configures Claude Code and Codex

Reuse

Borrowing it

Nothing to install: this file belongs to LooseWireDev/mealforge. 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/LooseWireDev/mealforge/main/.agents/skills/feature-development/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/LooseWireDev/mealforge

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/loosewiredev/mealforge/feature-development/github.svg)](https://agentmods.dev/skills/loosewiredev/mealforge/feature-development)

Your own site

<a href="https://agentmods.dev/skills/loosewiredev/mealforge/feature-development"><img src="https://agentmods.dev/badge/skills/loosewiredev/mealforge/feature-development/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/loosewiredev/mealforge/feature-development"><img src="https://agentmods.dev/badge/skills/loosewiredev/mealforge/feature-development.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 676 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.00048	$0.00676
Opus 5.5	$0.00019	$0.00270
Sonnet 5.5	$0.00010	$0.00135
Haiku 4.5	$0.00005	$0.00068

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

Security

Grade A, and why

feature-development 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.

.agents/skills/feature-development/SKILL.md · 51 lines

How it starts

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

Feature Development

Every feature follows the same four-step flow. Do not skip steps or reorder them.

1. Spec first

A feature starts from a written spec (usually in docs/) covering behavior, edge cases, and acceptance criteria. If no spec exists, stop and ask for one — do not improvise requirements.

2. Scaffold with the generator

npx nx generate @<project>/project-plugin:feature --name <name> --apps <apps>

<project> is this project's package scope (check the root package.json name or tools/project-plugin/package.json).
--name must be a camelCase identifier starting with a lowercase letter: userProfile, not user-profile or UserProfile. It becomes ${name}Router and directory names; the generator rejects anything else.
--apps is a comma-separated subset of api,web,mobile,desktop,static.

What the generator creates per app:

App	Files
api	`apps/api/src/features/<name>/` — `router.ts`, `service.ts`, `service.test.ts`, `types.ts`
web	`apps/web/src/features/<name>/` — `<Name>List.tsx`, `use<Name>Actions.ts`, `<Name>List.test.tsx`
mobile	`apps/mobile/src/features/<name>/` — same shape as web, React Native
desktop	`apps/desktop/src-tauri/src/commands/<name>.rs`
static	`apps/static/src/pages/<name>/index.astro` + island component

Plus, always: a shared Zod schema stub at packages/shared/src/schemas/<name>.ts and an AGENTS.md stub in each feature directory.

Wiring (Hono backends): the generator automatically registers the feature router in apps/api/src/trpc.ts via the // forge:feature-imports and // forge:feature-routers anchor comments. Do not remove those anchors, and do not wire routers by hand.

Python backends: the generator scaffolds client-side features only. Create the apps/api feature module manually following apps/api/AGENTS.md and the fastapi-sqlalchemy-patterns skill.

3. Failing tests (separate session/agent from implementation)

Write tests from the spec into the generated *.test.ts(x) files — never from reading implementation. Run them; they must fail for the right reason (missing behavior, not syntax errors).

Read the full file on GitHub · 51 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.

2mo ago First seen · 51 lines · 48 tokens per session scan A 6412e9f17b9c

Subscribe to this mod's changes

feature-development is a skill published in the GitHub repository LooseWireDev/mealforge (1 stars, last pushed 3mo ago), licensed MIT. It adds 48 tokens to every session and 676 once invoked, about $0.0002 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.

Planning ai-agents docker grocery-list homelab mcp mcp-server

feature-development next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
feature-developmentLooseWireDev/mealforge	Skill	1	3mo ago	MIT	A	48	Claude Code, Codex
knowledge-auditn24q02m/mnemo-mcp	Skill	11	1mo ago	Apache-2.0	A	21	Claude Code
temporal-queryn24q02m/mnemo-mcp	Skill	11	1mo ago	Apache-2.0	A	77	Claude Code
memory-commitn24q02m/mnemo-mcp	Skill	11	1mo ago	Apache-2.0	A	72	Claude Code
recall-contextn24q02m/mnemo-mcp	Skill	11	1mo ago	Apache-2.0	A	53	Claude Code
session-handoffn24q02m/mnemo-mcp	Skill	11	1mo ago	Apache-2.0	A	20	Claude Code
passport-bootstrapn24q02m/mnemo-mcp	Skill	11	1mo ago	Apache-2.0	A	83	Claude Code

mealforge: Skill for Claude Code