Menu
Create a new plan file in `.agents/plans/` for a feature or task.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
Drive the stella command-line client (@stll/cli), a legal-workspace CLI whose command surface is generated from the stella MCP tool registry. Covers install, OAuth login, the full command tree grouped by domain, JSON output for scripting, the --input escape hatch for deep payloads, cursor pagination, destructive-op confirmation, and exit codes.
Apply when writing or reviewing React effects in apps/web. Direct useEffect is banned; use the sanctioned wrappers or a better primitive.
Apply when writing or modifying database schema, queries, or migrations.
Apply when a performance-guard check (network baseline, bundle baseline, DB query count, loader-prefetch lint, RC bailouts) fails or when touching a hot route/endpoint.
Internationalization conventions for Stella. Apply when adding or modifying user-facing strings.
Apply when building or modifying user-facing UI components.
| name | plan |
| description | Create a new plan file in `.agents/plans/` for a feature or task. |
Create a new plan file in .agents/plans/ for a feature or task.
$ARGUMENTS — A short slug for the plan (kebab-case), e.g. "full-text-search" or "matter-lifecycle". If empty, determine an appropriate slug from the conversation context.
Read context — read .agents/ARCHITECTURE.md and .agents/GOALS.md
to understand the current system and priorities.
Determine the next plan number — list existing plans and increment:
ls .agents/plans/
Use the next sequential number (e.g., if 001-matters.md exists,
use 002).
Research the feature — before writing the plan, explore the codebase to understand what exists, what needs to change, and what the implications are. Read relevant handler files, schema, routes, and components.
Write the plan to .agents/plans/{number}-{slug}.md with this
structure:
# Plan: [Feature Name]
Date: YYYY-MM-DD
## Goal
What are we building and why? 1-3 sentences.
## Design Decisions
Key choices and why we made them. Focus on _what_ and _why_,
not prescriptive implementation details.
- **Decision 1**: Why this approach over alternatives.
- **Decision 2**: Why this approach over alternatives.
## Scope
**In scope:**
- ...
**Out of scope:**
- ...
## Implementation
Where the code lives and what changes. Be specific about files.
- `apps/api/src/...` — what changes here
- `apps/web/src/...` — what changes here
- DB schema changes (if any)
## Test Cases
What needs to be tested.
## Open Questions
Unresolved decisions (remove section when all resolved).
Plan guidelines:
Confirm with the user — show the plan and ask if they want to adjust anything before saving.