Skip to content
Back to skills

Plan

ASecurity

Use when the direction is chosen and the person wants a plan. Writes a high-level HTML cover sheet with package outcomes and explicit validation criteria. Never implements.

  • 9 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added September 23, 2026
ai-agentsgofrontendbackend

Works with

  • cli

Security analysis

A100/100

Pro scans all 6 files and shows the line behind each finding

Scanned November 10, 2026

npx -y skills add greenfield-inc/agent-farm --skill plan --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Plan?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Plan
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/greenfield-inc-plan-agent-farm/badge)](https://www.skillsdirectory.com/skills/greenfield-inc-plan-agent-farm)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: plan
description: Use when the direction is chosen and the person wants a plan. Writes a high-level HTML cover sheet with package outcomes and explicit validation criteria. Never implements.
---

# Plan

Write the context a capable implementer needs to build the feature. The approved cover sheet is the whole implementation handoff: it explains what to build and why, and leaves the step-by-step coding to the implementer.

## Establish the outcome

Start from the existing brief, approved design, and decisions. Settle genuine product choices with the person and leave routine implementation details to the implementer. A trivial task can use the existing one-sentence handoff instead of a plan. When alternatives are still open, use `options`.

Inspect enough of the repository to identify the affected surfaces, integration boundaries, existing patterns, and verification prerequisites. Link a few useful entry points when known. Keep investigation bounded: use an investigator only for a specific unknown that affects scope or validation. Leave test harnesses and environment repair to the implementer, and record what it must check during preflight, separating known blockers from assumptions.

## One output

Write `cover-sheet.html` in the work's existing bundle using the `page` standard and [references/cover-sheet.md](references/cover-sheet.md). The person and the implementer both read it. Keep its published identity and its links to the brief and approved designs.

Include:

- Outcome, scope and exclusions, high-level approach, constraints, locked decisions, and deferred items.
- Stacked package cards following [the presentation reference](references/presentation.md), each with concise approach notes: the outcome, how it will be built, systems to reuse or extend, any new systems and why, schema and data changes (or "none"), meaningful dependencies, and the relevant journey numbers or check names. Follow the package guidance in the cover-sheet reference, name confirmed integration points, and label assumptions. Packages are checkpoints for one implementer. Cover every affected client and entry path, including alternate composers and adapters.
- The **How we will know it works** section: numbered journeys and whole-feature commands or suites, each with an observable outcome and its prerequisites. Cover the backend, frontend, integration, and design behavior the feature needs, including identity, duplicate-name, and notification edge cases when they apply. Keep the checks specific to this task.
- When a package adds or changes a query on a hot path, its criteria name the worst-case production size and the budget it must meet. Passing on staging or test fixtures is not a worst case.
- Known environment and fixture needs, required whole-feature checks, and anything that cannot be exercised yet. Mark planned tests as planned; only an observed result counts as a pass. A missing capability leaves its criterion open.
- The review line at the top of the page, saying whether review runs and when:
  - Default: `Review: at the plan's end · Human review: none`: the implementer runs full validation (CI and QA) when the build is done, then `greenfield/reviewer` reviews the PR on its own, and again on the person's "ready" for tweaks added since.
  - `Human review: required | none`: required means the PR opens beside the person and no reviewer starts until they say "ready". Default to `required` when the plan changes UI, and `none` otherwise.
  - Options: none · this plan only · after named packages. Separately, the user may add a `greenfield/simplify-and-refactor` pass before QA and review.
  - Only the user changes it: record their explicit choice and when they made it. A mode you chose yourself does not count.
  - Standalone small change: a small, low-risk change may skip review without asking; say so up front and record the reason. Under an orchestrator, never skip on your own.

Keep the page short enough to read before coding. Explain the important technical approach and let the implementer choose files, signatures, and steps.

## Self-check and handoff

Before presenting the cover sheet, check it yourself against the brief and approved design:

- Scope, exclusions, constraints, and locked decisions agree. Packages cover the affected backend and frontend paths and explain the approach, reuse or extension, new systems, schema and data impact, and dependencies. Assumptions are labelled and required approvals are visible.
- **How we will know it works** covers required behavior, meaningful edge cases, and approved visual states, with observable outcomes and enough context to run each check. Prerequisites and blockers are recorded honestly, and planned checks are marked as planned.
- The page itself contains everything the person must review, including exact proposed copy or contract semantics when they matter. Important decisions and risks are visible above the package disclosures.
- The review line says whether review runs and when, with the person's choice or, for standalone small work, the skip reason. Contents and related-file links resolve, and Constraints and Non-goals are stacked vertically. Explicitly named entry points are confirmed with a quick look when needed.

Fix substantive gaps, mark the cover sheet **ready for approval**, and return its link. This is your own check, separate from user approval, so keep it quick: settled decisions stay settled and coding detail stays with the implementer. Socrates reviews the direction once, during `options`. Start implementation only when your role instructions separately authorize it; otherwise hand off as your role instructions describe.

When scope or a locked decision changes, revise the same cover sheet and its affected criteria. The implementer handles routine technical discoveries and extra in-scope caller files without a replan.

Files in this skill

  • SKILL.md3.1 KB
  • references/cover-sheet.md1.5 KB
  • references/handoff-card.md1.1 KB
  • references/levels.md1.1 KB
  • references/plan-md.md1.3 KB
  • references/work-package.md2.3 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

View all in ai-agents →

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.