Skip to content

JPeetz/agent-skills / skills/development/finding-unknowns/skills/implementation-plan

implementation-plan

Verified

Use when planning is requested before a build.

FileKindSize
CHANGELOG.mdmarkdown396 B
SKILL.mdskill md2.1 KB
evals/evals.jsonconfig2.4 KB

evals/evals.json

View on GitHub
{
  "skill": "implementation-plan",
  "version": "1.0.0",
  "cases": [
    {
      "id": "e1",
      "description": "Should trigger: planning requested before a build",
      "input": "Write an implementation plan before we start building the checkout redesign.",
      "shouldTrigger": true,
      "expect": "Produces a decision-first plan with tweakable decisions, known unknowns, compressed mechanical work",
      "assertions": [
        "Opens with 3-line summary including riskiest assumption",
        "Section 1 lists decisions user will likely tweak with alternatives and change costs",
        "Section 2 names known unknowns with defaults and pivot signals",
        "Section 3 compresses mechanical work",
        "Ends with 2-4 specific yes/no review items"
      ]
    },
    {
      "id": "e2",
      "description": "Should trigger: explicit plan request, modest scope",
      "input": "Can you plan the refactor of our auth module?",
      "shouldTrigger": true,
      "expect": "Produces an implementation plan ordering by likelihood-of-tweaking, not build order",
      "assertions": [
        "Plan reviewable in minutes",
        "Leaves room for improvisation during implementation"
      ]
    },
    {
      "id": "n1",
      "description": "Not trigger: no plan requested, direct build",
      "input": "Start building the feature now.",
      "shouldTrigger": false,
      "expect": "Proceeds to implementation",
      "assertions": [
        "No plan document produced"
      ]
    },
    {
      "id": "n2",
      "description": "Not trigger: brainstorming phase, not planning",
      "input": "What features could we add next quarter?",
      "shouldTrigger": false,
      "expect": "Brainstorms without a build plan",
      "assertions": [
        "No decision-first plan produced"
      ]
    },
    {
      "id": "e3",
      "description": "Should trigger: decisions-tweakable section for API shape choice",
      "input": "Plan the new API shape. There are two options \u2014 put the choice and what changing it later would cost in the plan.",
      "shouldTrigger": true,
      "expect": "Section 1 lists the API-shape decision with one alternative and the cost of changing later",
      "assertions": [
        "Opens with a three-line summary incl. riskiest assumption",
        "Lists the decision, one alternative, and change-later cost",
        "Names known unknowns with pivot signals",
        "Ends with 2-4 specific review items"
      ]
    }
  ]
}
planning-and-task-breakdownaddyosmani/agent-skillsBreaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible.Stars: 119kUpdated Claude CodeCodexVerifiedInstall
screenpipethedotmack/claude-memSearch screen and audio history recorded by Screenpipe and optionally save selected context into claude-mem. Use when the user asks to recall desktop activity, a meeting, or something seen in another app through Screenpipe.Stars: 118kUpdated Claude CodeCodexVerifiedInstall
contact-widgetnexu-io/open-designSelf-contained floating chat widget with welcome screen, social links, meeting button, and message input. Single HTML file, zero dependencies.Stars: 108kUpdated Claude CodeCodexVerifiedInstall
meeting-notesnexu-io/open-designMeeting notes page — title bar with attendees, agenda checklist, decisions block, action items table with owners + dates, and a "next meeting" footer. Use when the brief mentions "meeting notes", "minutes", "1:1 notes", "all-hands recap", or "会议纪要".Stars: 108kUpdated Claude CodeCodexVerifiedInstall