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

Spec

skill-artttj-rapid-stack-spec · by artttj

Use when a feature needs its spec — short clarifying Q&A, then docs/specs/<slug>/spec.md with a one-keypress self-approval gate.

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

Install

$ agentstack add skill-artttj-rapid-stack-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-artttj-rapid-stack-spec)

Reliability & compatibility

✓ Security review passed
0 installs to date
— no reviews yet
● 2mo ago

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 Spec? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

op:spec

Turn a feature ask into an approved spec. Write for your future executor: behavior and tests, not prose.

Steps

  1. Effort check: for a non-trivial feature, suggest raising to xhigh/max (arrow-choice), continue on answer.
  2. Clarify with at most 3 arrow-choice questions (purpose, constraints, success criteria). Skip what the ask already answers. For a genuinely unshaped problem use superpowers:brainstorming first; otherwise stay lean.
  3. Derive ``: kebab-case, 2–4 words, from the feature title.
  4. Write docs/specs//spec.md in the target repo:
---
status: draft
---
# 

## Goal
One paragraph: what exists after this ships, and why.

## Behavior
One bullet per observable behavior. Edge cases included.

## Architecture
Files to touch, data flow, integration points. Quote one real repo convention (file:line) this will follow.

## Tests
The named tests that prove Behavior.

## Out of scope
What this deliberately does not do.

## Open questions
Empty when approved.
  1. Present the spec, then the gate (arrow-choice): approve / edit / discard.
  • approve → set status: approved, add approved: , commit (docs: add spec), offer /op:plan as the next arrow-choice.
  • edit → apply, re-present.
  1. Hard stop: no plan and no code for this feature until status: approved and Open questions is empty.

Proof at end: the spec path and its frontmatter status.

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 AI & ML