AgentStack
Sign in Publish
MCP servers Skills Toolkits Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Write Plan

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

Generate or update implementation plan

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

Install

$ agentstack add skill-juliusz-cwiakalski-agentic-delivery-os-write-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 Write Plan? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Produce (or update) a fully structured IMPLEMENTATION PLAN from the canonical CHANGE SPECIFICATION.

User invocation: /write-plan

Writes (or updates): chg--plan.md in the same change folder as the spec.

$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-plan Example: /write-plan PDEV-123 ``

Given workItemRef:

  1. Search for folder: doc/changes/**/*----*/
  2. Locate spec: chg--spec.md
  3. If spec not found → FAIL

Files:

  • Spec: chg--spec.md
  • Plan: chg--plan.md
  • Branch: //
  1. Parse workItemRef from $ARGUMENTS
  2. Locate change folder and spec file per
  3. Extract slug, type, owners, etc. from spec front matter
  4. Checkout/create branch
  5. Delegate to @plan-writer agent (it has full template and rules)
  6. Report: path to created plan, next step: /write-test-plan or /run-plan

After successful execution:

  • Created/updated file path
  • Branch name
  • Recommendation: "Run /write-test-plan to generate the test plan, or /run-plan to begin execution"
  • Spec must exist; fail if not found
  • Only the plan file may be written
  • Derive all context from spec; do not invent

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