AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Planr Spec

skill-openplanr-openplanr-planr-spec · by openplanr

Shape vague product or engineering intent into a clear, measurable Protocol-compatible specification grounded in the current repository. Use when requirements need clarification before planning or implementation.

↗ Website ↗ Repository
— No reviews yet
0 installs
0 views
— view→install

Install

$ agentstack add skill-openplanr-openplanr-planr-spec

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

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-openplanr-openplanr-planr-spec)

Reliability & compatibility

✓ Security review passed
0 installs to date
— no reviews yet
● today

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Planr Spec? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Planr Spec

Shape vague product or engineering intent into a decision-complete specification inside this active coding session. Do not invoke a planning CLI or another model process.

Ground the specification

Read the request, repository instructions, ADRs, product documentation, existing planning artifacts, relevant implementation code and tests, stack configuration, design inputs, database context, and current behavior. Infer facts the repository already answers.

When a missing decision materially changes scope or observable behavior, use the host's structured question interface. Ask no more than three short, mutually exclusive questions at once and put the recommended option first. If the host lacks that interface, ask one concise chat question. Do not present a long prose questionnaire.

When native agents are available, use the specification role to consolidate the contract and dispatch database or designer roles only when their lens affects the decision. Otherwise perform those lenses sequentially in the active agent.

Author directly

Read [the specification contract](references/specification-contract.md). Write the specification to the repository's active planning layout, using a project-global monotonic SPEC-NNN ID. Inspect the repository's existing sequence and planning files before choosing it; never reuse a deleted ID.

Requirements and acceptance criteria must be observable. Put non-goals under out-of-scope boundaries. Record concrete repository paths and verification signals when they are known. Keep unresolved questions out of the saved contract when a repository-backed default exists.

Validate the completed artifact before returning. If a helper is unavailable, perform the same deterministic checks directly; never fall back to a model-backed CLI.

Return

  • Outcome: what the specification now defines.
  • Artifact: the saved path, or not saved for an explicitly inline result.
  • Decisions: locked decisions and grounded defaults.
  • Open question: only a decision that still changes the product; omit when

none remains.

  • Next: a copy-ready host-native planr-plan invocation for the saved spec.

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.

Write a review

Versions

  • v0.1.0 Imported from the upstream source.

More in Developer Tools