moonlight-lupin/agent-skills / plugins/dev-pipeline/skills/spec
spec
VerifiedUse when pinning intent before code — capture a spec (user stories, acceptance criteria, [NEEDS CLARIFICATION] markers), then plan the HOW (bite-sized tasks, blocking edges, gates) or slice tracer-bullet tickets. Triggers: 'write a spec', 'plan this', 'break this into tickets', 'slice this up', 'create tickets', 'what are the work units'.
references/goldfish/standards/heilmeier-standard.md
View on GitHub# Heilmeier Catechism Standard
This standard defines the quality bar for project proposals based on the
Heilmeier Catechism.
## Core Principle
A proposal passes if a competent engineer (or fresh AI session) who is
unfamiliar with the project can understand the goals, risks, and value of the
proposed work, and confirm that all catechism questions are answered without
ambiguity.
## Requirements (The Catechism Questions)
To satisfy this standard, the proposal must explicitly and clearly answer the
following questions:
* **Objectives**: What is being attempted? (Must be written with absolutely no
jargon).
* **State of the Art**: How is it done today, and what are the limits of
current practice?
* **New Approach**: What is new in the approach, and why is it expected to be
successful?
* **Impact**: Who cares? If successful, what difference will it make?
* **Risks**: What are the risks and the payoffs?
* **Cost**: How much will it cost in terms of resources, compute, or
headcount?
* **Timeline**: How long will it take?
* **Metrics & Exams**: What are the mid-term and final "exams" to check for
success?
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| 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: 119k | Updated | Claude CodeCodex | Verified | Install |
| 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: 118k | Updated | Claude CodeCodex | Verified | Install |
| 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: 108k | Updated | Claude CodeCodex | Verified | Install |
| 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: 108k | Updated | Claude CodeCodex | Verified | Install |