plan-author

Included with Lifetime

$97 forever

Linear hierarchical plan author. plan.md + phase-NN.md files with measurable success criteria and validation gates per phase.

General

What this skill does


# plan-author

Backs `/shannon:plan`, `/shannon:plan-tournament` (per candidate), `/shannon:plan-converge` (per round), `/shannon:plan-deep`, `/shannon:prd` (PRD mode).

## Behavior contract

1. Read user brief.
2. Read project context: `CLAUDE.md`, `docs/codebase-summary.md`, `docs/system-architecture.md`, `docs/code-standards.md`.
3. Decompose into phases. Each phase:
   - Atomic (can be executed and validated independently)
   - File-scoped (explicit list of files to modify/create/delete)
   - Has measurable success criteria
   - Has explicit validation gates
4. Write `plans/<date-prefix>-<slug>/`:
   - `plan.md` (overview, <80 lines, phase list with status)
   - `phase-01-<name>.md` ... `phase-NN-<name>.md`
5. Final phase is always validation (real-system exercise + evidence-gate) for any user-facing change.

## Phase file canonical structure

```markdown
# Phase NN: <name>

## Context Links
- Related reports / files / docs

## Overview
- Priority: <high | medium | low>
- Status: <pending | in_progress | completed>
- Description: <one paragraph>

## Key Insights
- <bullets from research / scout>

## Requirements
- Functional: <list>
- Non-functional: <perf, security, a11y>

## Architecture
- <diagrams or prose>

## Related Code Files
- Modify: <file paths>
- Create: <file paths>
- Delete: <file paths>

## Implementation Steps
1. <numbered>
2. ...

## Todo List
- [ ] <item>
- [ ] <item>

## Success Criteria
- <measurable; e.g. `curl /api/foo returns 200 with body matching schema-foo.json`>

## Validation Gate
- Skill: functional-validation
- Evidence required: <screenshot | API response | CLI stdout | build log>
- PASS criteria: <specific>

## Risk Assessment
- <likelihood × impact + mitigation>

## Security Considerations
- <auth, input validation, secrets>

## Next Steps
- Dependencies: <other phases>
- Follow-up: <future work>
```

## When to use

- `/shannon:plan` invocation
- `/shannon:plan-tournament` per-candidate spawn
- `/shannon:plan-converge` per-round spawn
- `/shannon:prd` PRD mode

## Iron rules

- Every phase has measurable success criteria — no "feature works" vague language.
- Every user-facing phase has a validation gate.
- No phase claims "tests pass" as success — phases never include test files.
- File ownership explicit per phase.

Files: 1

Size: 2.5 KB

Complexity: 10/100

Category: General

Source: https://github.com/krzemienski/shannon-framework/tree/main/modules/planning/skills/plan-author

Related in General

modeling-omnistudio-epc-catalog

Included

Salesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).

Generalscripts

relationship-science-coach

Included

Use this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.

Generalscripts

building-sf-integrations

Included

Salesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).

Generalscripts

venue-templates

Included

Access comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.

Generalscripts

let-fate-decide

Included

Draws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.

Generalscripts

net-ops

Included

Cross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.

Generalscripts