AgentStack
SKILL verified Apache-2.0 Self-run

Plan

skill-stella-skillguard-plan · by stella

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

No reviews yet
0 installs
5 views
0.0% view→install

Install

$ agentstack add skill-stella-skillguard-plan

✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

Are you the author of Plan? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

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

  1. Read planning context:
  • .agents/ARCHITECTURE.md if present
  • .agents/GOALS.md if present
  • recent related plans if present
  1. 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
  1. Determine the next plan number:

``bash 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.

  1. Research before writing:
  • inspect the existing code
  • read the relevant modules
  • understand constraints, patterns, and likely blast radius
  1. Write the plan with this structure:

```markdown # 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. ```

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

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet — be the first.

Versions

  • v0.1.0 Imported from the upstream source.