Agent Skills › stella/stella › plan

plan

GitHub

用于在.agents/plans/目录下为功能或任务创建新计划文件。需读取架构文档，确定序号，调研代码库后生成包含目标、设计决策、范围及实施细节的Markdown计划，并与用户确认。

.ai/local-skills/plan/SKILL.md stella/stella

Trigger Scenarios

需要为新功能或任务制定开发计划时用户请求创建项目规划文档时

Install

npx skills add stella/stella --skill plan -g -y

More Options

Non-standard path

npx skills add https://github.com/stella/stella/tree/main/.ai/local-skills/plan -g -y

Use without installing

npx skills use stella/stella@plan

指定 Agent (Claude Code)

npx skills add stella/stella --skill plan -a claude-code -g -y

安装 repo 全部 skill

npx skills add stella/stella --all -g -y

预览 repo 内 skill

npx skills add stella/stella --list

SKILL.md

Frontmatter

{
    "name": "plan",
    "description": "Create a new plan file in `.agents\/plans\/` for a feature or task."
}

Create Plan

Create a new plan file in .agents/plans/ for a feature or task.

Arguments

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

Instructions

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:
- Focus on what and why, avoid prescriptive how
- Consider both API layers: backend handlers and frontend routes
- Note DB schema changes explicitly — they affect migrations
- Flag security implications (ethical walls, workspace isolation, auth) per the security audit checklist
- Keep it concise — a plan is a thinking tool, not documentation
Confirm with the user — show the plan and ask if they want to adjust anything before saving.