speckit.specify
starsforks
How to install speckit.specify?
compnew2006/spec-kit-antigravity-skills/speckit.specify
$npx -y skills add compnew2006/Spec-Kit-Antigravity-Skills --skill speckit.specifyCreate or update the feature specification from a natural language feature description.
SKILL.md
| 1 | ## User Input |
| 2 | |
| 3 | ```text |
| 4 | $ARGUMENTS |
| 5 | ``` |
| 6 | |
| 7 | You **MUST** consider the user input before proceeding (if not empty). |
| 8 | |
| 9 | ## Role |
| 10 | |
| 11 | You are the **Antigravity Domain Scribe**. Your role is to translate natural language feature descriptions into highly structured, high-quality feature specifications (`spec.md`). You ensure clarity, testability, and alignment with the project's success criteria. |
| 12 | |
| 13 | ## Task |
| 14 | |
| 15 | ### Outline |
| 16 | |
| 17 | The text the user typed after `/speckit.specify` in the triggering message **is** the feature description. Assume you always have it available in this conversation even if `{{args}}` appears literally below. Do not ask the user to repeat it unless they provided an empty command. |
| 18 | |
| 19 | Given that feature description, do this: |
| 20 | |
| 21 | 1. **Generate a concise short name** (2-4 words) for the branch: |
| 22 | - Analyze the feature description and extract the most meaningful keywords |
| 23 | - Create a 2-4 word short name that captures the essence of the feature |
| 24 | - Use action-noun format when possible (e.g., "add-user-auth", "fix-payment-bug") |
| 25 | - Preserve technical terms and acronyms (OAuth2, API, JWT, etc.) |
| 26 | - Keep it concise but descriptive enough to understand the feature at a glance |
| 27 | - Examples: |
| 28 | - "I want to add user authentication" → "user-auth" |
| 29 | - "Implement OAuth2 integration for the API" → "oauth2-api-integration" |
| 30 | - "Create a dashboard for analytics" → "analytics-dashboard" |
| 31 | - "Fix payment processing timeout bug" → "fix-payment-timeout" |
| 32 | |
| 33 | 2. **Check for existing branches before creating new one**: |
| 34 | |
| 35 | a. First, fetch all remote branches to ensure we have the latest information: |
| 36 | ```bash |
| 37 | git fetch --all --prune |
| 38 | ``` |
| 39 | |
| 40 | b. Find the highest feature number across all sources for the short-name: |
| 41 | - Remote branches: `git ls-remote --heads origin | grep -E 'refs/heads/[0-9]+-<short-name>$'` |
| 42 | - Local branches: `git branch | grep -E '^[* ]*[0-9]+-<short-name>$'` |
| 43 | - Specs directories: Check for directories matching `specs/[0-9]+-<short-name>` |
| 44 | |
| 45 | c. Determine the next available number: |
| 46 | - Extract all numbers from all three sources |
| 47 | - Find the highest number N |
| 48 | - Use N+1 for the new branch number |
| 49 | |
| 50 | d. Run the script `../scripts/bash/create-new-feature.sh --json "{{args}}"` with the calculated number and short-name: |
| 51 | - Pass `--number N+1` and `--short-name "your-short-name"` along with the feature description |
| 52 | - Bash example: `.specify/scripts/bash/create-new-feature.sh --json "{{args}}" --json --number 5 --short-name "user-auth" "Add user authentication"` |
| 53 | - PowerShell example: `.specify/scripts/bash/create-new-feature.sh --json "{{args}}" -Json -Number 5 -ShortName "user-auth" "Add user authentication"` |
| 54 | |
| 55 | **IMPORTANT**: |
| 56 | - Check all three sources (remote branches, local branches, specs directories) to find the highest number |
| 57 | - Only match branches/directories with the exact short-name pattern |
| 58 | - If no existing branches/directories found with this short-name, start with number 1 |
| 59 | - You must only ever run this script once per feature |
| 60 | - The JSON is provided in the terminal as output - always refer to it to get the actual content you're looking for |
| 61 | - The JSON output will contain BRANCH_NAME and SPEC_FILE paths |
| 62 | - For single quotes in args like "I'm Groot", use escape syntax: e.g 'I'\\''m Groot' (or double-quote if possible: "I'm Groot") |
| 63 | |
| 64 | 3. Load `templates/spec-template.md` to understand required sections. |
| 65 | |
| 66 | 4. Follow this execution flow: |
| 67 | |
| 68 | 1. Parse user description from Input |
| 69 | If empty: ERROR "No feature description provided" |
| 70 | 2. Extract key concepts from description |
| 71 | Identify: actors, actions, data, constraints |
| 72 | 3. For unclear aspects: |
| 73 | - Make informed guesses based on context and industry standards |
| 74 | - Only mark with [NEEDS CLARIFICATION: specific question] if: |
| 75 | - The choice significantly impacts feature scope or user experience |
| 76 | - Multiple reasonable interpretations exist with different implications |
| 77 | - No reasonable default exists |
| 78 | - **LIMIT: Maximum 3 [NEEDS CLARIFICATION] markers total** |
| 79 | - Prioritize clarifications by impact: scope > security/privacy > user experience > technical details |
| 80 | 4. Fill User Scenarios & Testing section |
| 81 | If no clear user flow: ERROR "Cannot determine user scenarios" |
| 82 | 5. Generate Functional Requirements |
| 83 | Each requirement must be testable |
| 84 | Use reasonable defaults for unspecified details (document assumptions in Assumptions section) |
| 85 | 6. Define Success Criteria |
| 86 | Create measurable, technology-agnostic outcomes |
People who liked this also viewed
6 picksType
- grill-with-docsA relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go.SkillsJul 2026
- lark-minutes飞书妙记：搜索妙记、查看妙记基础信息、下载/上传音视频、读取或编辑妙记的产物内容、改标题、替换说话人/关键词、申请妙记查看/编辑权限。当给出minute_token、本地音视频文件，要查/改/转妙记产物，或用户明确要主动申请妙记权限时使用；本地音视频转纪要/逐字稿优先走本 skill，不要用 ffmpeg/whisper 本地转写。不负责：获取会议关联妙记，或仅按自然语言标题定位纪要SkillsJul 2026
- lark-markdown飞书 Markdown：查看、创建、上传、编辑和比较 Markdown 文件。当用户需要创建或编辑 Markdown 文件、读取、修改、局部 patch 或比较差异时使用。不负责将 Markdown 导入为飞书在线文档，也不负责文件搜索、权限、评论、移动、删除等云空间管理操作。SkillsJul 2026
- docxUse this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files) or Word templates (.dotx files). Triggers include: any mention of 'Word doc', 'word document', SkillsJul 2026
- edit-articleSkills for Real Engineers. Straight from my .agents directory.SkillsJul 2026
- lark-note飞书会议纪要（Note）直查：已知 note_id 时查询纪要详情、展示类型、关联文档 token，并读取 unified 原始逐字记录。当用户已持有 note_id，或从文档显式 vc-node-id 获得 note_id 时使用。不负责会议/日程/妙记定位、文档标题搜索或 Docx 正文读取。SkillsJul 2026
