AgentStack
SKILL verified MIT Self-run

Write Spec

skill-juliusz-cwiakalski-agentic-delivery-os-write-spec · by juliusz-cwiakalski

Generate canonical change specification

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

Install

$ agentstack add skill-juliusz-cwiakalski-agentic-delivery-os-write-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.

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

About

Generate a COMPLETE, implementation-agnostic CHANGE SPECIFICATION from planning session context.

User invocation: /write-spec

Inputs other than workItemRef MUST be sourced from the active planning context; NOTHING may be invented. Resulting spec becomes authoritative input for /write-plan.

$ARGUMENTS

  • workItemRef = first token matching pattern - (e.g., PDEV-123, GH-456)
  • If no valid workItemRef found, output NEEDS_INPUT:

`` NEEDS_INPUT: workItemRef required Usage: /write-spec Example: /write-spec PDEV-123 ``

Given workItemRef:

  1. Search for existing folder: doc/changes/**/*----*/
  2. If not found, create: doc/changes//----/

Files:

  • Spec: chg--spec.md
  • Branch: //
  1. Parse workItemRef from $ARGUMENTS
  2. Gather planning-session context from conversation
  3. Compute slug from title (lowercase kebab-case, ≤60 chars)
  4. Locate or create change folder per
  5. Determine change.type from context (feat/fix/refactor/etc.)
  6. Checkout/create branch
  7. Delegate to @spec-writer agent (it has the full template and rules)
  8. Report: path to created spec, next step: /write-plan

After successful execution:

  • Created file path
  • Branch name
  • Recommendation: "Run /write-plan to generate the implementation plan"
  • No implementation details in the spec
  • Only the spec file may be written
  • Await human approval before /write-plan

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.