Plan

Skill stella/skillguard/.agents/skills/plan

Local-first security scanner and policy gate for Agent Skills

Install

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

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Create a new implementation plan in the repo's planning area.

SKILL.md

2.1 KB, as published. Nobody here has run it

Create Plan

Create a new implementation plan in the repo's planning area.

Arguments

$ARGUMENTS — A short slug for the plan, ideally kebab-case. If empty, derive a reasonable slug from the task.

Conventions

Prefer this shared planning layout when the repo supports it:

.agents/ARCHITECTURE.md
.agents/GOALS.md
.agents/STATUS.md
.agents/plans/

If the repo uses a different planning area, adapt to it rather than creating duplicate systems.

Instructions

Read planning context:
- .agents/ARCHITECTURE.md if present
- .agents/GOALS.md if present
- recent related plans if present
Determine the plan location:
- prefer .agents/plans/
- if that directory does not exist, create it only if the repo is clearly adopting the shared planning convention
- otherwise ask or use the repo's existing planning area
Determine the next plan number:
```
ls .agents/plans/
```
Use the next sequential number when numbered plans are already in use. If the repo does not number plans, follow its established naming.
Research before writing:
- inspect the existing code
- read the relevant modules
- understand constraints, patterns, and likely blast radius

Write the plan with this structure:

# Plan: [Feature Name]

Date: YYYY-MM-DD

## Goal

What are we building and why?

## Design Decisions

- **Decision**: Why this approach over alternatives.

## Scope

**In scope:**
- ...

**Out of scope:**
- ...

## Implementation

- `path/to/file` — what changes here

## Test Cases

What needs to be verified.

## Open Questions

Any unresolved decisions.

Plan well, do not over-specify:
- focus on what and why
- avoid locking in incidental implementation details too early
- call out migrations, security implications, and rollout risk when relevant
Confirm before finalizing if the user is still shaping the task. If they asked you to just create the plan, go ahead and write it.