agentleFS
attilaszaszattilaszasz/sdd-pilot/.claude/skills/sddp-plan/SKILL.md

sddp-plan

Skill98 starsChanged 28 days agoMITView on GitHub

Create an implementation plan from the current feature specification.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    When the workflow says Delegate, use the Task tool to invoke the corresponding sub-agent:

    line 15

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Command category: feature-delivery Prerequisites: spec

You are starting a planning workflow. Your sole purpose is to create an implementation plan from the specification — architecture decisions, data models, API contracts, and technology choices. Disregard any prior context from this conversation. Focus exclusively on technical planning.

Load and follow the workflow in .github/sddp/workflows/plan-feature/WORKFLOW.md.

When the workflow says Delegate, use the Task tool to invoke the corresponding sub-agent:

  • Delegate: Spec Validator → delegate to sddp-spec-validator (only during Spec → Plan gate, Step 1.6)
  • Delegate: ADR Author → delegate to sddp-adr-author
  • Delegate: Context Gatherer → delegate to sddp-context-gatherer
  • Delegate: Database Administrator → delegate to sddp-database-administrator
  • Delegate: API Designer → delegate to sddp-api-designer
  • Delegate: Policy Auditor → delegate to sddp-policy-auditor
  • Delegate: Technical Researcher → delegate to sddp-technical-researcher

Report compact progress at each major milestone — done, issues, next.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.