[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75QAD81HVTM7GFE08PPFTNG":3,"skill-same:01M75QAD81HVTM7GFE08PPFTNG":49},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":28,"commitSha":29,"skillDirectory":30,"forksCount":14,"repositoryHtmlUrl":31,"repositoryHomepageUrl":6,"ownerHtmlUrl":32,"ownerBlogUrl":33,"ownerDescription":6,"updatedAt":34,"install":35,"resources":48},"01M75QAD81HVTM7GFE08PPFTNG","speckit-companion-specify",null,"Companion specify — a feature spec with prioritized user stories","mictlanix\u002Fmbe-ui","mictlanix","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F703184?v=4","01M75Q1XD9477GXRKPM6JVVC11","Mictlanix","01M75Q1XDXKYX3VS9T3CS2XEFR",0,"MIT","https:\u002F\u002Fgithub.com\u002Fmictlanix\u002Fmbe-ui\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fspeckit-companion-specify\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: speckit-companion-specify\ndescription: Companion specify — a feature spec with prioritized user stories\ncompatibility: Requires spec-kit project structure with .specify\u002F directory\nmetadata:\n  author: github-spec-kit\n  source: companion:commands\u002Fspeckit.companion.specify.md\n---\n\n## User Input\n\n```text\n$ARGUMENTS\n```\n\n\u003C!-- speckit-companion:part step-start -->\n## Record this step's start, before anything else runs\n\nLet `\u003Cstep>`\u002F`\u003Cstatus>` be this command's phase and in-progress status: `specify`\u002F`specifying`, `plan`\u002F`planning`, `tasks`\u002F`tasking`, `implement`\u002F`implementing`. A step that mints its own feature directory (`specify`, `auto`) resolves it first, because `.specify\u002Ffeature.json` still points at the previous spec; every other step stamps at once, before any hook or node:\n\n```bash\npython3 .specify\u002Fextensions\u002Fcompanion\u002Fscripts\u002Fwrite-context.py --feature-dir \u003Cfeature_directory> --step \u003Cstep> --status \u003Cstatus> --kind start --by extension\n```\n\nAdd `--at \"\u003Cdispatch time>\"` when the dispatcher printed one. Run it, never hand-write it. A second start is refused, so running it is always safe.\n\u003C!-- \u002Fspeckit-companion:part step-start -->\n\n\u003C!-- speckit-companion:part command-spelling -->\n## Name every command the way this project registers it\n\nCommands are named in dot form throughout this body, `speckit.companion.plan`, because that is their canonical id, and without a leading slash, because the spelling a host actually registers is not always this one. Claude Code installs `\u002Fspeckit-companion-plan`. Look at how the commands are installed in this project, under the agent's own commands or skills directory, and use that spelling every time you name one to the developer or dispatch one yourself. A dotted name typed into a host that registered dashes resolves to nothing at all.\n\u003C!-- \u002Fspeckit-companion:part command-spelling -->\n\n\u003C!-- speckit-companion:part speckit-hooks -->\n## Stock spec-kit extension hooks\n\nOnly if `.specify\u002Fextensions.yml` lists entries under `hooks.before_\u003Cstep>` or `hooks.after_\u003Cstep>`, where `\u003Cstep>` is this command's phase, read `.specify\u002Fextensions\u002Fcompanion\u002Fcommands\u002Freference\u002Fspeckit-hooks.md` and follow it: the `before_` pass now, before any work below, and the `after_` pass once this command's work is reported. Otherwise skip this.\n\u003C!-- \u002Fspeckit-companion:part speckit-hooks -->\n\n\u003C!-- speckit-companion:part concise -->\n## The smallest thing that works\n\n**Stop at the first rung that holds:** does it need to exist; does this codebase already have it; does the platform or an installed dependency do it; can it be one line; only then, the minimum code. Fix the cause where every caller passes through. No interface with one implementation, no factory for one product, no scaffolding for later. Lean governs what you build, not how work is split.\n\n**Write it the way you would say it.** One idea per sentence, no em-dashes, no \"shall be capable of\", no section that says \"N\u002FA\". Then reread and cut: the sentence that restates the one before, the example longer than its rule, the clause defending a choice nobody challenged.\n\n**Never simplify away** validation at a trust boundary, error handling that prevents data loss, security, accessibility, or anything the spec asks for. **A corner cut on purpose** carries `\u002F\u002F simplified: \u003Cceiling>, \u003Cwhat to do when it binds>` in the code and one `concerns` entry in this step's capture.\n\u003C!-- \u002Fspeckit-companion:part concise -->\n\n## Outline\n\nProduce a feature specification: prioritized user stories with acceptance scenarios, functional requirements, key entities, edge cases, and measurable success criteria, then a quality checklist.\n\u003C!-- speckit-companion:phase gather -->\n\u003C!-- speckit-companion:node resolve-dir -->\n1. **Resolve the feature directory. Mint a fresh dir for new work.** `.specify\u002Ffeature.json` is an **output** of this step, never an input: it points at the *previous* spec, so reusing it would clobber finished work. On a project's first run it is absent or zero-byte, which means the same thing. Pick the target:\n   - If the request names a target path (or `SPECIFY_FEATURE_DIRECTORY` is set), use it.\n   - Otherwise derive a 2–4 word short-name from the description and run `python3 .specify\u002Fextensions\u002Fcompanion\u002Fscripts\u002Fmint-spec-dir.py --short-name \"\u003Cshort-name>\"`. It creates the next folder, numbered the way this project's `feature_numbering` says and safe against a run started at the same time, points `.specify\u002Ffeature.json` at it, and prints its path. Never pick the number yourself. The spec file is `\u003Cfeature_directory>\u002Fspec.md`. **Never write into a directory that already contains a feature spec (`spec.md`, or an older `*.spec.md`)**: that's a prior spec, not this one.\n   For a named target, create `\u003Cfeature_directory>\u002F` and point `.specify\u002Ffeature.json` at it by writing `{\"feature_directory\": \"\u003Cfeature_directory>\"}`. Later capture calls resolve the spec through that exact key when they run without `--feature-dir`, so any other key silently drops those writes.\n   Then stamp the **specify START** as the step-start instruction above directs: the directory exists now, so run it before any other work.\n\n   Right after the stamp, store the request word for word: the user input this command received, exactly as given, never a summary. Pass it on stdin so quotes and line breaks survive:\n   ```bash\n   python3 .specify\u002Fextensions\u002Fcompanion\u002Fscripts\u002Fwrite-context.py --feature-dir \u003Cfeature_directory> --request - \u003C\u003C'COMPANION_REQUEST'\n   \u003Cthe user input, unchanged>\n   COMPANION_REQUEST\n   ```\n   The record keeps the first request it is given, so when auto started this run and stored its own, this call changes nothing.\n\u003C!-- \u002Fspeckit-companion:node resolve-dir -->\n\u003C!-- \u002Fspeckit-companion:phase gather -->\n\u003C!-- speckit-companion:phase classify -->\n\u003C!-- speckit-companion:node classify-size -->\n**Classify the change before drafting, to right-size the ceremony.** Decide now, from the request and **one bounded look at the code** (at most three reads or searches, enough to know what and where to change), whether this change can go straight to implement or needs the full specify → plan → tasks → implement pipeline. Deciding first means a small change never pays for documents it does not need. This is a best-effort heuristic and **MUST err toward `normal`** only where it matters: when a high-risk item might apply, or the outcome or where to change it is still unclear after the bounded look. Being cautious about an understood, contained change is not a reason to call it normal.\n\n\u003C!-- speckit-companion:part sizing -->\n- **small** when all three hold:\n  1. **Understood**: the outcome is stated, you know what and where to change, and no product or design decision is open.\n  2. **Contained risk**: it touches none of these, where a mistake is hard to see or hard to undo: changing or deleting existing stored data or a stored format (a migration; saving new records is fine); security (auth, permissions, secrets); a contract others already consume (a public API, CLI flag, config format or export, changed or removed; adding one is fine); concurrency (locks, races, ordering); delivery (installers, release, CI, dependencies); or behavior no test would catch if it broke.\n  3. **Resumable from the diff**: if the session stopped now, someone could finish from the request and `git diff` alone.\n\n  A change of up to about 5 files and 10 tasks that touches none of the items in 2 is small: several files of one understood change do not make it normal. Counts alone never make a change large.\n- **oversized**: the change clearly spans several subsystems, or is roughly double the size one session handles comfortably (more than about 10 files or 20 tasks).\n- **normal**: anything in between (the default).\n\u003C!-- \u002Fspeckit-companion:part sizing -->\n\n   Record your estimates as you go: `projectedFiles` and `projectedTasks`, and a `scopeSignal` from the wording (`\"larger\"` for rewrite | overhaul | new system | migration | redesign | …; `\"smaller\"` for one-line | rename | typo | tweak | copy change | …; else `\"none\"`). They are context for a later reader, not the rule. Then:\n\n   ```\n   verdict = \"simple\"    if  the change is **small** by all three tests above\n                         and scopeSignal != \"larger\"\n             \"oversized\" if  the oversized bar above holds\n             else \"normal\"\n   ```\n\n   When the verdict is not `simple` because a high-risk item applies, print this line verbatim, naming the item, then run the branch the verdict names:\n\n   ```\n   [companion] Change touches \u003Cthe high-risk item> — running the full pipeline as \u003Cnormal|oversized>.\n   ```\n\u003C!-- \u002Fspeckit-companion:node classify-size -->\n\u003C!-- speckit-companion:node persist-size -->\n**Carry the size verdict into the wrap-up call**, so `plan` and `tasks` can right-size their output without re-deciding it. Do not record it on its own: the finalize step's single `--batch` takes it, with the classification's **inputs** so a later resume can judge whether the call was borderline or clear-cut. Add both to that call:\n   ```json\n   \"set\": {\"size\": \"\u003Csimple|normal|oversized>\", …},\n   \"classification\": {\"projectedFiles\": \u003Cn>, \"projectedTasks\": \u003Cn>, \"scopeSignal\": \"\u003Clarger|smaller|none>\", \"verdict\": \"\u003Csimple|normal|oversized>\"}\n   ```\n   Write `simple` when the change is the small, fast-trackable size; `oversized` when it crossed the guardrail; otherwise `normal`. Neither field touches the lifecycle log.\n\u003C!-- \u002Fspeckit-companion:node persist-size -->\n\u003C!-- \u002Fspeckit-companion:phase classify -->\n\u003C!-- speckit-companion:phase author -->\n\u003C!-- speckit-companion:node draft-spec -->\n**Where the request names two or more code areas and you have a subagent tool, dispatch one read-only worker per area first**, each returning the files that area exposes and the conventions it follows, never file contents. Those findings are what you record as `context` in the wrap-up and what plan reads. One area, or no subagent tool: look yourself.\n\n2. Create `\u003Cfeature_directory>\u002Fspec.md` with these sections, in order, for a business stakeholder: **what** users need and **why**, not **how**. Backticks only for literal identifiers a reader would copy. When the brief names a ticket id or URL (`TODO-42`, `#931`, an issue link), or carries a `Source:` line naming an assessment folder, put one `**Source**: \u003Cticket>` line under the title, copied exactly (the first, when it names several; the rest go under Assumptions); never fetch the ticket, the id or URL is data.\n\n   - **User Scenarios & Testing** *(mandatory)*: prioritized user stories, each an independently testable slice. Per story: `### User Story N - \u003Cshort title> (Priority: P1|P2|P3)` and a one-paragraph journey; **Why this priority** in one line; **Independent Test**, how this story alone proves value; **Acceptance Scenarios**, numbered `**Given** … **When** … **Then** …`. P1 first, as many stories as the feature needs.\n   - **Edge Cases**: the boundary and error questions the implementation must answer (empty input, removal while in use, duplicates, reload and persistence).\n   - **Requirements › Functional Requirements** *(mandatory)*: numbered `FR-001…`, each one testable MUST\u002FSHOULD statement. A genuinely unresolvable choice is `[NEEDS CLARIFICATION: …]` (max 3); prefer an informed default recorded under Assumptions.\n   - **Key Entities** *(when the feature involves data)*: what each represents, its key attributes and relationships, no implementation detail.\n   - **Success Criteria › Measurable Outcomes** *(mandatory)*: technology-agnostic `SC-001…` outcomes (time, count, percentage, pass\u002Ffail).\n   - **Assumptions**: the defaults you chose for anything the request left open.\n   - **Verbatim Constraints** *(only when the request pins exact values)*: every literal the result must match (a `data-testid`, route, endpoint, CLI flag, env var, config key, exact UI copy, column name), in backticks, exactly as written. Never paraphrase, recase or rename them; downstream steps use these exact strings. This is the one place implementation detail belongs in a spec.\n\n3. Tighten every requirement until it is testable and unambiguous, and remove a section that does not apply. Carry the Functional Requirements into the wrap-up call as `coverage`, each with its one-line text as `title`.\n\u003C!-- \u002Fspeckit-companion:node draft-spec -->\n\u003C!-- speckit-companion:node quality-checklist -->\n4. **Self-check the spec once, in place.** Do not write a checklist file. Read `spec.md` against these, fix each fail in the spec, and leave a genuine ambiguity as a `[NEEDS CLARIFICATION: …]` marker (max 3) for `clarify`. One pass, no rewrite loop, no option tables:\n\n   - No implementation detail outside **Verbatim Constraints**; written for a non-technical reader.\n   - User Scenarios, Functional Requirements and Success Criteria are present.\n   - Each requirement is one testable MUST\u002FSHOULD statement with acceptance criteria behind it.\n   - Success criteria are measurable and technology-agnostic.\n   - Edge cases, scope, dependencies and assumptions are stated.\n\u003C!-- \u002Fspeckit-companion:node quality-checklist -->\n\u003C!-- \u002Fspeckit-companion:phase author -->\n\u003C!-- speckit-companion:phase wrap-up -->\n\u003C!-- speckit-companion:node branch -->\n7. **Branch on the verdict.**\n\n   - **`simple`, minimal mode.** Write **three lean files** in this one pass so the file-driven views (top stepper, sidebar, implement progress) reconcile with the history-driven fold. Never a single combined spec file:\n     - Append an **Approach** section to the already-written `spec.md`: the files to touch and any dependencies, in a few bullets. This is the plan content, inline, and stays the plan source-of-truth.\n     - Write `\u003Cfeature_directory>\u002Fplan.md` as a **short pointer** to the spec's Approach (say, a one-line blockquote linking `.\u002Fspec.md#approach` and `.\u002Ftasks.md`). Do **not** duplicate the approach bullets; `plan.md` references them.\n     - Write `\u003Cfeature_directory>\u002Ftasks.md` carrying the **real task checklist**: a dependency-ordered list, one per line as `- [ ] **T001** [P?] \u003Cdescription> + \u003Cpath>` (`[P]` marks tasks that can run in parallel). This MUST be the actual checklist, not a pointer: implement progress counts these checkboxes, so a pointer would read 0\u002F0. Include one test task per requirement, testing it through the public surface in the condition it states.\n\n     Put the task checklist **only** in `tasks.md`. A second copy in the spec would drift. `spec.md` keeps the Approach; `tasks.md` owns the tasks.\n\n     Do **not** run `speckit.companion.plan` or `speckit.companion.tasks`: the three lean files plus the lifecycle fold below record those steps as satisfied.\n   - **`normal`, full pipeline.** Write `spec.md` only: no appended Approach section, no `plan.md` \u002F `tasks.md` here, no lifecycle fold. Plan and tasks are produced and recorded by their own `speckit.companion.plan` and `speckit.companion.tasks` runs.\n\u003C!-- \u002Fspeckit-companion:node branch -->\n\u003C!-- speckit-companion:node finalize -->\n**Output**: `\u003Cfeature_directory>\u002Fspec.md`. In **simple** mode the spec additionally carries an **Approach** section, and two lean files sit alongside it: `plan.md` (a pointer to that Approach) and `tasks.md` (the real `- [ ] **T001** …` checklist; the task list lives here, not in the spec). In **normal** mode the spec holds the four sections only, and no `plan.md` \u002F `tasks.md` are written here.\n\n**Capture the whole wrap-up in one call.** Everything this step learned goes in a single `--batch`: what it worked *from* (the areas investigated, the constraints honored), the distilled intent, the explicit non-goals, and the workflow identity.\n\n```bash\npython3 .specify\u002Fextensions\u002Fcompanion\u002Fscripts\u002Fwrite-context.py --feature-dir \u003Cfeature_directory> --batch '{\n  \"context\": [\"area: \u003Cpath or subsystem>\", \"constraint: \u003Crule honored>\"],\n  \"expectations\": [\"\u003Cout-of-scope item>\", \"\u003Canother>\"],\n  \"coverage\": [{\"req\": \"FR-001\", \"title\": \"\u003Cthe requirement's one-line text>\"}],\n  \"set\": {\"intent\": \"\u003Cone-line goal>\", \"workflow\": \"companion\", \"size\": \"\u003Cverdict>\"},\n  \"classification\": {\"projectedFiles\": \u003Cn>, \"projectedTasks\": \u003Cn>, \"scopeSignal\": \"\u003Clarger|smaller|none>\", \"verdict\": \"\u003Cverdict>\"}\n}'\n```\n\nBest-effort as a whole: skip silently if `python3` is unavailable. Omit `context` when there is nothing worth recording and `expectations` when the spec declares no non-goals; never invent either. A spec with a `**Source**:` line adds `\"source\": \"\u003Cthat ticket, as written>\"` to `set`, and one the brief says extends or supersedes an earlier folder adds `\"extends\"` or `\"supersedes\"` with that folder. **`workflow` is the one field that is not optional**: without it the shared writer defaults to `speckit`, and a later footer advance dispatches the stock command.\n\n**On a `simple` run, add the approach to the same call.** A `simple` run writes its plan inline and never reaches `plan`, where a full run records it. So when `verdict == \"simple\"`, put `\"approach\": \"\u003Cone-line summary of the Approach section>\"` in the `set` map alongside the rest rather than paying a second call.\n\n**Record completion.** After `spec.md` is written, close the specify step. The extension stamps the real end, so do **not** hand-write an `ai` complete for specify:\n```bash\npython3 .specify\u002Fextensions\u002Fcompanion\u002Fscripts\u002Fwrite-context.py --feature-dir \u003Cfeature_directory> --step specify --status specified --kind complete --by extension\n```\n\n**Fast-path lifecycle fold (simple mode only).** When `verdict == \"simple\"`, record the folded `plan` and `tasks` steps so the history-driven panels read them as satisfied-by-fast-path and the spec lands ready for implement. One call, **after** the specify completion above, writes all four boundaries in order (plan start and complete, tasks start and complete) in a single write, so the fold lands whole or not at all. It is idempotent. Do not hand-write the boundaries, and do not run it for a `normal` verdict:\n```bash\npython3 .specify\u002Fextensions\u002Fcompanion\u002Fscripts\u002Fwrite-context.py --feature-dir \u003Cfeature_directory> --fold plan,tasks --by extension\n```\nAfter the fold, the spec sits at the **tasks** step with `status: ready-to-implement`; the developer triggers implement next. Do **not** write a `completed` status: the final completed gate stays a user action.\n\u003C!-- \u002Fspeckit-companion:node finalize -->\n\u003C!-- speckit-companion:node handoff -->\n\u003C!-- speckit-companion:part timing -->\n## Timing: keep `.spec-context.json` honest\n\nRecord every boundary by **running the writer script**, never by editing `.spec-context.json`. The model is **finish-only**: one finish per task and per substep, timed from the previous one; never a `start`+`complete` pair. **One shell call per moment**: writes that happen together go in one call chained with `&&`, because every separate call is a turn that re-reads the whole session. **In a single-quoted `--batch '{…}'`, write an apostrophe as `'`**, or pass `--batch -` with the JSON on stdin; never debug the quoting by reading the script.\n\n- **Close your own step** as your last action, after any mandatory after-hook block. Specify already closed itself in its wrap-up; clarify and analyze use `--finish` instead. Implement ends at `implemented`; converge completes the spec.\n\n  ```bash\n  python3 .specify\u002Fextensions\u002Fcompanion\u002Fscripts\u002Fwrite-context.py --feature-dir \u003Cfeature_dir> --step \u003Cthis step> --advance --by ai\n  ```\n\n- **One finish per substep, the moment it ends, when the step runs on its own**; inside an auto run, skip them. Plan records `research` and `design`, tasks `generate`.\n\n  ```bash\n  python3 .specify\u002Fextensions\u002Fcompanion\u002Fscripts\u002Fwrite-context.py --feature-dir \u003Cfeature_dir> --step \u003Cstep> --substep \u003Cname> --finish --by ai\n  ```\n\n- **Close each wave the moment its last task is done**, in one call listing its tasks. It checks their boxes and times the wave as one unit. Never hand-edit a box; closing several waves at once is a defect the doctor reports.\n\n  ```bash\n  python3 .specify\u002Fextensions\u002Fcompanion\u002Fscripts\u002Fwrite-context.py --feature-dir \u003Cfeature_dir> --close-task \u003CT001,T002,…> --by ai --did \"\u003Cone line>\" --files \"\u003Cfiles>\"\n  ```\n\n  **A fanned-out worker appends only**, because two folders contend; the main agent folds each returned result with `--materialize`, one at a time:\n\n  ```bash\n  python3 .specify\u002Fextensions\u002Fcompanion\u002Fscripts\u002Fwrite-context.py --feature-dir \u003Cfeature_dir> --task \u003CTaskID> --kind complete --by ai --did \"\u003Cone line>\" --files \"\u003Cfiles>\" --append\n  ```\n\n- **Never write the next step's start.** The next command owns it.\n\u003C!-- \u002Fspeckit-companion:part timing -->\n\n**The next step is `plan`**: dispatch `speckit.companion.plan \u003Cfeature_dir>`. Unless this spec was classified `simple`, in which case plan and tasks are already folded and the next step is `implement`: `speckit.companion.implement \u003Cfeature_dir>`.\n\n\u003C!-- speckit-companion:part self-advance -->\n## After this step\n\nInside a Companion auto run, or when the input says `workflow engine step`, the orchestrator decides what runs next: skip this. Otherwise, once this step's work is done, read `.specify\u002Fextensions\u002Fcompanion\u002Fcommands\u002Freference\u002Fself-advance.md` and follow it.\n\u003C!-- \u002Fspeckit-companion:part self-advance -->\n\u003C!-- \u002Fspeckit-companion:node handoff -->\n\u003C!-- \u002Fspeckit-companion:phase wrap-up -->\n\n\u003C!-- speckit-companion:part orchestrator -->\n## Node hooks\n\nA project can attach its own work around this command's nodes in `.specify\u002Fcompanion.yml`. **Only if that file declares `commands.\u003Cthis-command>.hooks`**, read `.specify\u002Fextensions\u002Fcompanion\u002Fcommands\u002Freference\u002Fnode-hooks.md` and follow it. Otherwise there are no hooks: skip this and run the command as written.\n\u003C!-- \u002Fspeckit-companion:part orchestrator -->\n","## User Input\n\n```text\n$ARGUMENTS\n```\n\n\u003C!-- speckit-companion:part step-start -->\n## Record this step's start, before anything else runs\n\nLet `\u003Cstep>`\u002F`\u003Cstatus>` be this command's phase and in-progress status: `specify`\u002F`specifying`, `plan`\u002F`planning`, `tasks`\u002F`tasking`, `implement`\u002F`implementing`. A step that mints its own feature directory (`specify`, `auto`) resolves it first, because `.specify\u002Ffeature.json` still points at the previous spec; every other step stamps at once, before any hook or node:\n\n```bash\npython3 .specify\u002Fextensions\u002Fcompanion\u002Fscripts\u002Fwrite-context.py --feature-dir \u003Cfeature_directory> --step \u003Cstep> --status \u003Cstatus> --kind start --by extension\n```\n\nAdd `--at \"\u003Cdispatch time>\"` when the dispatcher printed one. Run it, never hand-write it. A second start is refused, so running it is always safe.\n\u003C!-- \u002Fspeckit-companion:part step-start -->\n\n\u003C!-- speckit-companion:part command-spelling -->\n## Name every command the way this project registers it\n\nCommands are named in dot form throughout this body, `speckit.companion.plan`, because that is their canonical id, and without a leading slash, because the spelling a host actually registers is not always this one. Claude Code installs `\u002Fspeckit-companion-plan`. Look at how the commands are installed in this project, under the agent's own commands or skills directory, and use that spelling every time you name one to the developer or dispatch one yourself. A dotted name typed into a host that registered dashes resolves to nothing at all.\n\u003C!-- \u002Fspeckit-companion:part command-spelling -->\n\n\u003C!-- speckit-companion:part speckit-hooks -->\n## Stock spec-kit extension hooks\n\nOnly if `.specify\u002Fextensions.yml` lists entries under `hooks.before_\u003Cstep>` or `hooks.after_\u003Cstep>`, where `\u003Cstep>` is this command's phase, read `.specify\u002Fextensions\u002Fcompanion\u002Fcommands\u002Freference\u002Fspeckit-hooks.md` and follow it: the `before_` pass now, before any work below, and the `after_` pass once this command's work is reported. Otherwise skip this.\n\u003C!-- \u002Fspeckit-companion:part speckit-hooks -->\n\n\u003C!-- speckit-companion:part concise -->\n## The smallest thing that works\n\n**Stop at the first rung that holds:** does it need to exist; does this codebase already have it; does the platform or an installed dependency do it; can it be one line; only then, the minimum code. Fix the cause where every caller passes through. No interface with one implementation, no factory for one product, no scaffolding for later. Lean governs what you build, not how work is split.\n\n**Write it the way you would say it.** One idea per sentence, no em-dashes, no \"shall be capable of\", no section that says \"N\u002FA\". Then reread and cut: the sentence that restates the one before, the example longer than its rule, the clause defending a choice nobody challenged.\n\n**Never simplify away** validation at a trust boundary, error handling that prevents data loss, security, accessibility, or anything the spec asks for. **A corner cut on purpose** carries `\u002F\u002F simplified: \u003Cceiling>, \u003Cwhat to do when it binds>` in the code and one `concerns` entry in this step's capture.\n\u003C!-- \u002Fspeckit-companion:part concise -->\n\n## Outline\n\nProduce a feature specification: prioritized user stories with acceptance scenarios, functional requirements, key entities, edge cases, and measurable success criteria, then a quality checklist.\n\u003C!-- speckit-companion:phase gather -->\n\u003C!-- speckit-companion:node resolve-dir -->\n1. **Resolve the feature directory. Mint a fresh dir for new work.** `.specify\u002Ffeature.json` is an **output** of this step, never an input: it points at the *previous* spec, so reusing it would clobber finished work. On a project's first run it is absent or zero-byte, which means the same thing. Pick the target:\n   - If the request names a target path (or `SPECIFY_FEATURE_DIRECTORY` is set), use it.\n   - Otherwise derive a 2–4 word short-name from the description and run `python3 .specify\u002Fextensions\u002Fcompanion\u002Fscripts\u002Fmint-spec-dir.py --short-name \"\u003Cshort-name>\"`. It creates the next folder, numbered the way this project's `feature_numbering` says and safe against a run started at the same time, points `.specify\u002Ffeature.json` at it, and prints its path. Never pick the number yourself. The spec file is `\u003Cfeature_directory>\u002Fspec.md`. **Never write into a directory that already contains a feature spec (`spec.md`, or an older `*.spec.md`)**: that's a prior spec, not this one.\n   For a named target, create `\u003Cfeature_directory>\u002F` and point `.specify\u002Ffeature.json` at it by writing `{\"feature_directory\": \"\u003Cfeature_directory>\"}`. Later capture calls resolve the spec through that exact key when they run without `--feature-dir`, so any other key silently drops those writes.\n   Then stamp the **specify START** as the step-start instruction above directs: the directory exists now, so run it before any other work.\n\n   Right after the stamp, store the request word for word: the user input this command received, exactly as given, never a summary. Pass it on stdin so quotes and line breaks survive:\n   ```bash\n   python3 .specify\u002Fextensions\u002Fcompanion\u002Fscripts\u002Fwrite-context.py --feature-dir \u003Cfeature_directory> --request - \u003C\u003C'COMPANION_REQUEST'\n   \u003Cthe user input, unchanged>\n   COMPANION_REQUEST\n   ```\n   The record keeps the first request it is given, so when auto started this run and stored its own, this call changes nothing.\n\u003C!-- \u002Fspeckit-companion:node resolve-dir -->\n\u003C!-- \u002Fspeckit-companion:phase gather -->\n\u003C!-- speckit-companion:phase classify -->\n\u003C!-- speckit-companion:node classify-size -->\n**Classify the change before drafting, to right-size the ceremony.** Decide now, from the request and **one bounded look at the code** (at most three reads or searches, enough to know what and where to change), whether this change can go straight to implement or needs the full specify → plan → tasks → implement pipeline. Deciding first means a small change never pays for documents it does not need. This is a best-effort heuristic and **MUST err toward `normal`** only where it matters: when a high-risk item might apply, or the outcome or where to change it is still unclear after the bounded look. Being cautious about an understood, contained change is not a reason to call it normal.\n\n\u003C!-- speckit-companion:part sizing -->\n- **small** when all three hold:\n  1. **Understood**: the outcome is stated, you know what and where to change, and no product or design decision is open.\n  2. **Contained risk**: it touches none of these, where a mistake is hard to see or hard to undo: changing or deleting existing stored data or a stored format (a migration; saving new records is fine); security (auth, permissions, secrets); a contract others already consume (a public API, CLI flag, config format or export, changed or removed; adding one is fine); concurrency (locks, races, ordering); delivery (installers, release, CI, dependencies); or behavior no test would catch if it broke.\n  3. **Resumable from the diff**: if the session stopped now, someone could finish from the request and `git diff` alone.\n\n  A change of up to about 5 files and 10 tasks that touches none of the items in 2 is small: several files of one understood change do not make it normal. Counts alone never make a change large.\n- **oversized**: the change clearly spans several subsystems, or is roughly double the size one session handles comfortably (more than about 10 files or 20 tasks).\n- **normal**: anything in between (the default).\n\u003C!-- \u002Fspeckit-companion:part sizing -->\n\n   Record your estimates as you go: `projectedFiles` and `projectedTasks`, and a `scopeSignal` from the wording (`\"larger\"` for rewrite | overhaul | new system | migration | redesign | …; `\"smaller\"` for one-line | rename | typo | tweak | copy change | …; else `\"none\"`). They are context for a later reader, not the rule. Then:\n\n   ```\n   verdict = \"simple\"    if  the change is **small** by all three tests above\n                         and scopeSignal != \"larger\"\n             \"oversized\" if  the oversized bar above holds\n             else \"normal\"\n   ```\n\n   When the verdict is not `simple` because a high-risk item applies, print this line verbatim, naming the item, then run the branch the verdict names:\n\n   ```\n   [companion] Change touches \u003Cthe high-risk item> — running the full pipeline as \u003Cnormal|oversized>.\n   ```\n\u003C!-- \u002Fspeckit-companion:node classify-size -->\n\u003C!-- speckit-companion:node persist-size -->\n**Carry the size verdict into the wrap-up call**, so `plan` and `tasks` can right-size their output without re-deciding it. Do not record it on its own: the finalize step's single `--batch` takes it, with the classification's **inputs** so a later resume can judge whether the call was borderline or clear-cut. Add both to that call:\n   ```json\n   \"set\": {\"size\": \"\u003Csimple|normal|oversized>\", …},\n   \"classification\": {\"projectedFiles\": \u003Cn>, \"projectedTasks\": \u003Cn>, \"scopeSignal\": \"\u003Clarger|smaller|none>\", \"verdict\": \"\u003Csimple|normal|oversized>\"}\n   ```\n   Write `simple` when the change is the small, fast-trackable size; `oversized` when it crossed the guardrail; otherwise `normal`. Neither field touches the lifecycle log.\n\u003C!-- \u002Fspeckit-companion:node persist-size -->\n\u003C!-- \u002Fspeckit-companion:phase classify -->\n\u003C!-- speckit-companion:phase author -->\n\u003C!-- speckit-companion:node draft-spec -->\n**Where the request names two or more code areas and you have a subagent tool, dispatch one read-only worker per area first**, each returning the files that area exposes and the conventions it follows, never file contents. Those findings are what you record as `context` in the wrap-up and what plan reads. One area, or no subagent tool: look yourself.\n\n2. Create `\u003Cfeature_directory>\u002Fspec.md` with these sections, in order, for a business stakeholder: **what** users need and **why**, not **how**. Backticks only for literal identifiers a reader would copy. When the brief names a ticket id or URL (`TODO-42`, `#931`, an issue link), or carries a `Source:` line naming an assessment folder, put one `**Source**: \u003Cticket>` line under the title, copied exactly (the first, when it names several; the rest go under Assumptions); never fetch the ticket, the id or URL is data.\n\n   - **User Scenarios & Testing** *(mandatory)*: prioritized user stories, each an independently testable slice. Per story: `### User Story N - \u003Cshort title> (Priority: P1|P2|P3)` and a one-paragraph journey; **Why this priority** in one line; **Independent Test**, how this story alone proves value; **Acceptance Scenarios**, numbered `**Given** … **When** … **Then** …`. P1 first, as many stories as the feature needs.\n   - **Edge Cases**: the boundary and error questions the implementation must answer (empty input, removal while in use, duplicates, reload and persistence).\n   - **Requirements › Functional Requirements** *(mandatory)*: numbered `FR-001…`, each one testable MUST\u002FSHOULD statement. A genuinely unresolvable choice is `[NEEDS CLARIFICATION: …]` (max 3); prefer an informed default recorded under Assumptions.\n   - **Key Entities** *(when the feature involves data)*: what each represents, its key attributes and relationships, no implementation detail.\n   - **Success Criteria › Measurable Outcomes** *(mandatory)*: technology-agnostic `SC-001…` outcomes (time, count, percentage, pass\u002Ffail).\n   - **Assumptions**: the defaults you chose for anything the request left open.\n   - **Verbatim Constraints** *(only when the request pins exact values)*: every literal the result must match (a `data-testid`, route, endpoint, CLI flag, env var, config key, exact UI copy, column name), in backticks, exactly as written. Never paraphrase, recase or rename them; downstream steps use these exact strings. This is the one place implementation detail belongs in a spec.\n\n3. Tighten every requirement until it is testable and unambiguous, and remove a section that does not apply. Carry the Functional Requirements into the wrap-up call as `coverage`, each with its one-line text as `title`.\n\u003C!-- \u002Fspeckit-companion:node draft-spec -->\n\u003C!-- speckit-companion:node quality-checklist -->\n4. **Self-check the spec once, in place.** Do not write a checklist file. Read `spec.md` against these, fix each fail in the spec, and leave a genuine ambiguity as a `[NEEDS CLARIFICATION: …]` marker (max 3) for `clarify`. One pass, no rewrite loop, no option tables:\n\n   - No implementation detail outside **Verbatim Constraints**; written for a non-technical reader.\n   - User Scenarios, Functional Requirements and Success Criteria are present.\n   - Each requirement is one testable MUST\u002FSHOULD statement with acceptance criteria behind it.\n   - Success criteria are measurable and technology-agnostic.\n   - Edge cases, scope, dependencies and assumptions are stated.\n\u003C!-- \u002Fspeckit-companion:node quality-checklist -->\n\u003C!-- \u002Fspeckit-companion:phase author -->\n\u003C!-- speckit-companion:phase wrap-up -->\n\u003C!-- speckit-companion:node branch -->\n7. **Branch on the verdict.**\n\n   - **`simple`, minimal mode.** Write **three lean files** in this one pass so the file-driven views (top stepper, sidebar, implement progress) reconcile with the history-driven fold. Never a single combined spec file:\n     - Append an **Approach** section to the already-written `spec.md`: the files to touch and any dependencies, in a few bullets. This is the plan content, inline, and stays the plan source-of-truth.\n     - Write `\u003Cfeature_directory>\u002Fplan.md` as a **short pointer** to the spec's Approach (say, a one-line blockquote linking `.\u002Fspec.md#approach` and `.\u002Ftasks.md`). Do **not** duplicate the approach bullets; `plan.md` references them.\n     - Write `\u003Cfeature_directory>\u002Ftasks.md` carrying the **real task checklist**: a dependency-ordered list, one per line as `- [ ] **T001** [P?] \u003Cdescription> + \u003Cpath>` (`[P]` marks tasks that can run in parallel). This MUST be the actual checklist, not a pointer: implement progress counts these checkboxes, so a pointer would read 0\u002F0. Include one test task per requirement, testing it through the public surface in the condition it states.\n\n     Put the task checklist **only** in `tasks.md`. A second copy in the spec would drift. `spec.md` keeps the Approach; `tasks.md` owns the tasks.\n\n     Do **not** run `speckit.companion.plan` or `speckit.companion.tasks`: the three lean files plus the lifecycle fold below record those steps as satisfied.\n   - **`normal`, full pipeline.** Write `spec.md` only: no appended Approach section, no `plan.md` \u002F `tasks.md` here, no lifecycle fold. Plan and tasks are produced and recorded by their own `speckit.companion.plan` and `speckit.companion.tasks` runs.\n\u003C!-- \u002Fspeckit-companion:node branch -->\n\u003C!-- speckit-companion:node finalize -->\n**Output**: `\u003Cfeature_directory>\u002Fspec.md`. In **simple** mode the spec additionally carries an **Approach** section, and two lean files sit alongside it: `plan.md` (a pointer to that Approach) and `tasks.md` (the real `- [ ] **T001** …` checklist; the task list lives here, not in the spec). In **normal** mode the spec holds the four sections only, and no `plan.md` \u002F `tasks.md` are written here.\n\n**Capture the whole wrap-up in one call.** Everything this step learned goes in a single `--batch`: what it worked *from* (the areas investigated, the constraints honored), the distilled intent, the explicit non-goals, and the workflow identity.\n\n```bash\npython3 .specify\u002Fextensions\u002Fcompanion\u002Fscripts\u002Fwrite-context.py --feature-dir \u003Cfeature_directory> --batch '{\n  \"context\": [\"area: \u003Cpath or subsystem>\", \"constraint: \u003Crule honored>\"],\n  \"expectations\": [\"\u003Cout-of-scope item>\", \"\u003Canother>\"],\n  \"coverage\": [{\"req\": \"FR-001\", \"title\": \"\u003Cthe requirement's one-line text>\"}],\n  \"set\": {\"intent\": \"\u003Cone-line goal>\", \"workflow\": \"companion\", \"size\": \"\u003Cverdict>\"},\n  \"classification\": {\"projectedFiles\": \u003Cn>, \"projectedTasks\": \u003Cn>, \"scopeSignal\": \"\u003Clarger|smaller|none>\", \"verdict\": \"\u003Cverdict>\"}\n}'\n```\n\nBest-effort as a whole: skip silently if `python3` is unavailable. Omit `context` when there is nothing worth recording and `expectations` when the spec declares no non-goals; never invent either. A spec with a `**Source**:` line adds `\"source\": \"\u003Cthat ticket, as written>\"` to `set`, and one the brief says extends or supersedes an earlier folder adds `\"extends\"` or `\"supersedes\"` with that folder. **`workflow` is the one field that is not optional**: without it the shared writer defaults to `speckit`, and a later footer advance dispatches the stock command.\n\n**On a `simple` run, add the approach to the same call.** A `simple` run writes its plan inline and never reaches `plan`, where a full run records it. So when `verdict == \"simple\"`, put `\"approach\": \"\u003Cone-line summary of the Approach section>\"` in the `set` map alongside the rest rather than paying a second call.\n\n**Record completion.** After `spec.md` is written, close the specify step. The extension stamps the real end, so do **not** hand-write an `ai` complete for specify:\n```bash\npython3 .specify\u002Fextensions\u002Fcompanion\u002Fscripts\u002Fwrite-context.py --feature-dir \u003Cfeature_directory> --step specify --status specified --kind complete --by extension\n```\n\n**Fast-path lifecycle fold (simple mode only).** When `verdict == \"simple\"`, record the folded `plan` and `tasks` steps so the history-driven panels read them as satisfied-by-fast-path and the spec lands ready for implement. One call, **after** the specify completion above, writes all four boundaries in order (plan start and complete, tasks start and complete) in a single write, so the fold lands whole or not at all. It is idempotent. Do not hand-write the boundaries, and do not run it for a `normal` verdict:\n```bash\npython3 .specify\u002Fextensions\u002Fcompanion\u002Fscripts\u002Fwrite-context.py --feature-dir \u003Cfeature_directory> --fold plan,tasks --by extension\n```\nAfter the fold, the spec sits at the **tasks** step with `status: ready-to-implement`; the developer triggers implement next. Do **not** write a `completed` status: the final completed gate stays a user action.\n\u003C!-- \u002Fspeckit-companion:node finalize -->\n\u003C!-- speckit-companion:node handoff -->\n\u003C!-- speckit-companion:part timing -->\n## Timing: keep `.spec-context.json` honest\n\nRecord every boundary by **running the writer script**, never by editing `.spec-context.json`. The model is **finish-only**: one finish per task and per substep, timed from the previous one; never a `start`+`complete` pair. **One shell call per moment**: writes that happen together go in one call chained with `&&`, because every separate call is a turn that re-reads the whole session. **In a single-quoted `--batch '{…}'`, write an apostrophe as `'`**, or pass `--batch -` with the JSON on stdin; never debug the quoting by reading the script.\n\n- **Close your own step** as your last action, after any mandatory after-hook block. Specify already closed itself in its wrap-up; clarify and analyze use `--finish` instead. Implement ends at `implemented`; converge completes the spec.\n\n  ```bash\n  python3 .specify\u002Fextensions\u002Fcompanion\u002Fscripts\u002Fwrite-context.py --feature-dir \u003Cfeature_dir> --step \u003Cthis step> --advance --by ai\n  ```\n\n- **One finish per substep, the moment it ends, when the step runs on its own**; inside an auto run, skip them. Plan records `research` and `design`, tasks `generate`.\n\n  ```bash\n  python3 .specify\u002Fextensions\u002Fcompanion\u002Fscripts\u002Fwrite-context.py --feature-dir \u003Cfeature_dir> --step \u003Cstep> --substep \u003Cname> --finish --by ai\n  ```\n\n- **Close each wave the moment its last task is done**, in one call listing its tasks. It checks their boxes and times the wave as one unit. Never hand-edit a box; closing several waves at once is a defect the doctor reports.\n\n  ```bash\n  python3 .specify\u002Fextensions\u002Fcompanion\u002Fscripts\u002Fwrite-context.py --feature-dir \u003Cfeature_dir> --close-task \u003CT001,T002,…> --by ai --did \"\u003Cone line>\" --files \"\u003Cfiles>\"\n  ```\n\n  **A fanned-out worker appends only**, because two folders contend; the main agent folds each returned result with `--materialize`, one at a time:\n\n  ```bash\n  python3 .specify\u002Fextensions\u002Fcompanion\u002Fscripts\u002Fwrite-context.py --feature-dir \u003Cfeature_dir> --task \u003CTaskID> --kind complete --by ai --did \"\u003Cone line>\" --files \"\u003Cfiles>\" --append\n  ```\n\n- **Never write the next step's start.** The next command owns it.\n\u003C!-- \u002Fspeckit-companion:part timing -->\n\n**The next step is `plan`**: dispatch `speckit.companion.plan \u003Cfeature_dir>`. Unless this spec was classified `simple`, in which case plan and tasks are already folded and the next step is `implement`: `speckit.companion.implement \u003Cfeature_dir>`.\n\n\u003C!-- speckit-companion:part self-advance -->\n## After this step\n\nInside a Companion auto run, or when the input says `workflow engine step`, the orchestrator decides what runs next: skip this. Otherwise, once this step's work is done, read `.specify\u002Fextensions\u002Fcompanion\u002Fcommands\u002Freference\u002Fself-advance.md` and follow it.\n\u003C!-- \u002Fspeckit-companion:part self-advance -->\n\u003C!-- \u002Fspeckit-companion:node handoff -->\n\u003C!-- \u002Fspeckit-companion:phase wrap-up -->\n\n\u003C!-- speckit-companion:part orchestrator -->\n## Node hooks\n\nA project can attach its own work around this command's nodes in `.specify\u002Fcompanion.yml`. **Only if that file declares `commands.\u003Cthis-command>.hooks`**, read `.specify\u002Fextensions\u002Fcompanion\u002Fcommands\u002Freference\u002Fnode-hooks.md` and follow it. Otherwise there are no hooks: skip this and run the command as written.\n\u003C!-- \u002Fspeckit-companion:part orchestrator -->\n",{"name":5,"metadata":24,"description":7,"compatibility":27},{"author":25,"source":26},"github-spec-kit","companion:commands\u002Fspeckit.companion.specify.md","Requires spec-kit project structure with .specify\u002F directory","main","76d33ff49e8de1e5f77412aeba2d7e5602e442ed",".claude\u002Fskills\u002Fspeckit-companion-specify","https:\u002F\u002Fgithub.com\u002Fmictlanix\u002Fmbe-ui","https:\u002F\u002Fgithub.com\u002Fmictlanix","https:\u002F\u002Fmictlanix.com","2026-11-15 04:02:27",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add mictlanix\u002Fmbe-ui --skill speckit-companion-specify",{"tool":41,"command":42},"bunx","bunx skills add mictlanix\u002Fmbe-ui --skill speckit-companion-specify",{"tool":44,"command":45},"pnpm","pnpm dlx skills add mictlanix\u002Fmbe-ui --skill speckit-companion-specify","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmictlanix\u002Fmbe-ui\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fspeckit-companion-specify\u002FSKILL.md",true,[],[50,57,62,69,76,83],{"skillNo":51,"name":52,"nameZh":6,"description":53,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":54,"categories":55,"keywords":56,"publishedAt":19},"01M75QCZHHB42Q7KJTZHQZXZ77","speckit-wireframes-draft","Draw low-fi wireframes for every screen and state the spec describes","https:\u002F\u002Fgithub.com\u002Fmictlanix\u002Fmbe-ui\u002Fblob\u002Fmain\u002F.specify\u002Fextensions\u002Fwireframes\u002F.specify-dev\u002Fagent-commands\u002Fclaude\u002Fspeckit-wireframes-draft\u002FSKILL.md",[],[],{"skillNo":58,"name":52,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":19},"01M75QCXRSD7HM7AFZH4HA9E6S","https:\u002F\u002Fgithub.com\u002Fmictlanix\u002Fmbe-ui\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fspeckit-wireframes-draft\u002FSKILL.md",[],[],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":19},"01M75QCVS17DXXBTQ8DE2SSXVR","speckit-taskstoissues","Convert existing tasks into actionable, dependency-ordered GitHub issues for the feature based on available design artifacts.","https:\u002F\u002Fgithub.com\u002Fmictlanix\u002Fmbe-ui\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fspeckit-taskstoissues\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M75QCS3M02XD4PW58EXS6458","speckit-tasks","Generate an actionable, dependency-ordered tasks.md for the feature based on available design artifacts.","https:\u002F\u002Fgithub.com\u002Fmictlanix\u002Fmbe-ui\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fspeckit-tasks\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M75QCP9NASXGDNYZF6XYJZBD","speckit-specify","Create or update the feature specification from a natural language feature description.","https:\u002F\u002Fgithub.com\u002Fmictlanix\u002Fmbe-ui\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fspeckit-specify\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M75QCKBPS4K60R4YPRQ8HBJ9","speckit-plan","Execute the implementation planning workflow using the plan template to generate design artifacts.","https:\u002F\u002Fgithub.com\u002Fmictlanix\u002Fmbe-ui\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fspeckit-plan\u002FSKILL.md",[],[]]