Borrowing it
Nothing to install: this file belongs to phuoctrung-ppt/ai-sdlc-workflow. 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/phuoctrung-ppt/ai-sdlc-workflow/master/.cursor/commands/plan-feature.mdgit clone --depth 1 https://github.com/phuoctrung-ppt/ai-sdlc-workflowWrote 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/commands/phuoctrung-ppt/ai-sdlc-workflow/plan-feature)<a href="https://agentmods.dev/commands/phuoctrung-ppt/ai-sdlc-workflow/plan-feature"><img src="https://agentmods.dev/badge/commands/phuoctrung-ppt/ai-sdlc-workflow/plan-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.
<a href="https://agentmods.dev/commands/phuoctrung-ppt/ai-sdlc-workflow/plan-feature"><img src="https://agentmods.dev/badge/commands/phuoctrung-ppt/ai-sdlc-workflow/plan-feature.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.00038 | $0.00700 |
| Opus 5.5 | $0.00015 | $0.00280 |
| Sonnet 5.5 | $0.00008 | $0.00140 |
| Haiku 4.5 | $0.00004 | $0.00070 |
Grade A, and why
plan-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 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.
What it actually says
Act as Architect Planner (.cursor/agents/architect-planner.md).
Feature: {feature_description}
- Run context-builder:
python3 .cursor/context/context-builder.py --phase plan --task "{feature_description}" --agent architect-planner --handoff docs/plans/.active-plan - Resolve profile — read
AGENTS.md §0and/or.cursor/config/active-layers.json.- If §0 missing: ask user to fill profile + layers, or run
python3 .cursor/context/profile-sync.py --detectthen confirm. - Layer off = absent — do not plan migrations, tenancy, queues, or assign workers for that layer.
- If §0 missing: ask user to fill profile + layers, or run
- Phase 0 BRAINSTORM (HARD-GATE): explore codebase, propose 2–3 options, wait for approval — do not write the plan file yet.
- Read
.memory/architecture.mdandAGENTS.md §0–§3 for profile, stack, structure. - Explore codebase for related modules (only paths that exist for active layers).
- Write plan to
docs/plans/YYYY-MM-DD-{slug}.mdusing the architect-planner template (include Domain Config Sync). - Conditional plan body (include only if layer is on):
| Layer on | May include |
|---|---|
| database | Migration needs, entities |
| backend | API / service tasks, shared contracts |
| frontend | UI tasks, Design Contract gate if new visible UI |
| multi-tenancy | Tenant isolation notes |
| queue | Job/queue notes |
| auth | Auth/RBAC notes |
| devops | Deploy/CI notes |
| ai-llm | LLM cost/safety notes |
Always include: Goal, acceptance criteria, file list with owner agents ⊆ active agents, task table, risks, scope boundaries.
For every off layer relevant to the feature, one line only:
N/A — layer <name> off (AGENTS.md §0).
Forbidden: unconditional "Database migration needs" or tenancy sections when those layers are off.
- Phase 1.5 SYNC DOMAIN CONFIG (before workers):
- ADR →
docs/adr/when architecture/stack/pattern decisions changed - Create/update
docs/architecture.mdonly for active-layer surfaces - Update
AGENTS.mdonly sections that changed and whose layer is on (§4 only if multi-tenancy on, §9 only if database on, §14 only if queue on) - Update
worker-scopes.json/protected-paths.jsonif scopes changed (orchestrator approval for expansion) - Re-run
python3 .cursor/context/profile-sync.py --from-agentsif §0 or §3 changed - Point
docs/plans/.active-planat this plan - Record N/A + reason for skipped sync items
- ADR →
- Wait for orchestrator approval of plan + sync diffs before dispatching workers (use
@scaffold-agentfirst if new module shells are required).
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 Changed · +17 lines · +14 tokens per session c704f0f6bc9f
- 1mo ago First seen · 31 lines · 24 tokens per session scan A 71252d51d5ba
plan-feature is a command published in the GitHub repository phuoctrung-ppt/ai-sdlc-workflow (2 stars, last pushed 1mo ago), licensed MIT. It adds 38 tokens to every session and 700 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.
Other commands, from other repositories
init
Initialize configurations for Supabase local development.
http-service
Build, review or debug a Bun HTTP service. Loads the http-service skill, then works the task through its workflow.
api-contract-review
Review an API contract (shapes, errors, auth model) BEFORE implementation for naming, versioning, pagination, idempotency, and fit with existing endpoints. Use when designing or changing endpoints. Do not use when the API is already implemented (use review-hard or repo-consistency-sweep).
build
Discover an AI Gateway's models and MCP tools, retrieve a credential, and integrate them into your app — call a model, connect MCP tools, or scaffold a runnable agent.
start-10-1
A guided lesson on setting up clasp, a command-line tool for managing Google Apps Script projects, and connecting it to Google’s Apps Script API.
fastapi
FastAPI application design and implementation conventions. Use this skill when building, updating, or reviewing FastAPI services, routers, dependencies, request/response schemas, streaming endpoints, or API tests. Trigger on FastAPI-specific work such as path operation design, dependency injection, response models…