Prompt file imported from B0yZ4kr14/OrthoPlus-Enterprise (.github/prompts/speckit.time.machine.next.prompt.md). Fill in {{arguments}} before use. Copyright stays with the author.

speckit.time.machine.next

Name: speckit.time.machine.next
Author: B0yZ4kr14

Description

Instructions

name: speckit-time-machine-next description: Run the full SDD workflow for every pending feature in the Time Machine queue, sequentially compatibility: Requires spec-kit project structure with .specify/ directory metadata: author: github-spec-kit source: time-machine:commands/next.md

Time Machine — Next Feature

Process every pending feature in the queue one after the other without stopping between them. For each feature the full spec-kit SDD lifecycle runs: specify → clarify → plan → tasks → implement. After each implementation the user is asked whether to push the branch. Declining does not stop the loop — the next feature starts immediately. A final summary is shown when all features are done.

User Input

Accepted flags:

--feature <id> — start (or resume) from a specific feature instead of the next pending one
--from <phase> — when used with --feature, resume that feature from a specific phase (specify, clarify, plan, tasks, implement)
--include-skipped — re-run all previously skipped features after any remaining pending ones
--redo <id> — force re-run a specific feature regardless of its current status (pending, in-progress, done, or skipped)

Steps

This command runs a loop. Repeat Steps 1–10 for every remaining pending feature in order. Do not stop between features. Only exit the loop when all eligible features are done or skipped, then proceed to Step 11. When --include-skipped is passed, skipped features are included in the run. When --redo <id> is passed, only that single feature is processed regardless of status.

1. Load and validate the queue

Read .specify/extensions/time-machine/features-queue.yml.

If the file does not exist → stop and tell the user: "No queue found. Run /speckit.time-machine.analyze first."
If --redo <id> was passed:
- Find the feature with that id regardless of its current status.
- If not found → stop: "No feature with id '<id>' found in the queue."
- Reset it: status: pending, clear completed_at, branch, pushed, started_at.
- The loop runs for only this one feature.
Otherwise:
- Collect every feature where status is pending or in-progress, in order.
- For any collected feature where status is in-progress and current_phase is set, automatically treat it as if --from <current_phase> was passed for that feature. Print: "Resuming '<Feature Name>' from phase: <current_phase>"
- If --include-skipped was also passed, append every skipped feature (in original order) and reset each to status: pending.
- If --feature <id> was passed → start the loop from that feature only (skip any features before it in the collected list).
- If no eligible features remain → skip straight to Step 11.

2. Mark as in-progress

For the current feature, update features-queue.yml:

status: in-progress
started_at: "<current ISO 8601 timestamp>" # only if not already set

Print:

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Time Machine — Feature <#N of total>
  ID:    <feature-id>
  Name:  <Feature Name>
  Files: <comma-separated list>
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

3. Create a git branch

git checkout -b feature/time-machine-<feature-id>

If the branch already exists (resuming), run git checkout feature/time-machine-<feature-id> instead.
Update features-queue.yml → branch: "feature/time-machine-<feature-id>".
If git is not initialised, warn the user and continue without branching.

4. Phase: Specify

[Phase 1/5] Specify — "<Feature Name>"

Update features-queue.yml → current_phase: specify.

Run /speckit.specify scoped to this feature, passing:

"Feature: . Description: . Relevant files: . Focus on this feature only; do not modify other features."

Wait for the spec to be written before continuing. If --from is set to a later phase, skip this step.

5. Phase: Clarify

[Phase 2/5] Clarify — "<Feature Name>"

Update features-queue.yml → current_phase: clarify.

Run /speckit.clarify for this feature.

Human gate: present every generated question to the user and wait for answers before proceeding. Do not auto-answer or skip.

If --from is set to a later phase, skip this step.

6. Phase: Plan

[Phase 3/5] Plan — "<Feature Name>"

Update features-queue.yml → current_phase: plan.

Run /speckit.plan for this feature. Wait for the plan to be written. If --from is set to a later phase, skip this step.

7. Phase: Tasks

[Phase 4/5] Tasks — "<Feature Name>"

Update features-queue.yml → current_phase: tasks.

Run /speckit.tasks for this feature. Wait for tasks to be generated. If --from is set to a later phase, skip this step.

8. Phase: Implement

[Phase 5/5] Implement — "<Feature Name>"

Update features-queue.yml → current_phase: implement.

Run /speckit.implement for this feature. Wait for implementation to complete.

9. Satisfaction gate

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Feature "<Feature Name>" implemented.

Satisfied with the result?
  yes      — continue to the next feature
  redo     — re-run from a specific phase
  skip     — skip this feature and move on
  wrap up  — mark done, commit, and stop for now
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

yes → proceed to Step 10.
redo → ask "Which phase? [specify / clarify / plan / tasks / implement]" then loop back to the relevant step above.
skip → update status: skipped, completed_at: <now>, pushed: null, current_phase: null. Print a one-line skip notice then continue immediately to the next feature (go back to Step 2 with the next pending feature).
wrap up → mark the feature complete, commit all changes on the current branch, then stop:
1. Run git add -A && git commit -m "feat(time-machine): complete <feature-id>".
2. Update features-queue.yml: status: done, completed_at: <now>, current_phase: null, pushed: false.
3. Print:
```
Feature "<Feature Name>" marked complete and committed.
Run /speckit.time-machine.next to continue with the next feature.
```
4. Exit the loop. Do not proceed to Step 10 or 11.

10. Push gate

Ask the user:

Push branch "feature/time-machine-<feature-id>" to remote? [yes / no]

If yes:

Run git push -u origin feature/time-machine-<feature-id>.
Update features-queue.yml: pushed: true.
Print a one-line confirmation.

If no:

Update features-queue.yml: pushed: false.
Print nothing extra — immediately continue to the next feature.

Either way, update the feature:

status: done
completed_at: "<current ISO 8601 timestamp>"
current_phase: null

Then go back to Step 2 with the next pending feature.

11. All features done — final report

Reached when every eligible feature is done or skipped.

If --redo <id> was used, "eligible" means just that one feature.
If --include-skipped was used, previously skipped features that were re-run now count toward done/pushed.

Collect all features where pushed: false (declined) and status: done.

If every done feature was pushed (pushed: true or pushed: null for skipped):

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 Time Machine complete! 🎉

 All <N> features have been specced and implemented.

   ✓ Pushed:   <N>
   ↷ Skipped:  <N>
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

If any done features were NOT pushed (pushed: false):

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 Time Machine complete!

 Here's a summary of all branches created:

  Branch                                  Status
  ──────────────────────────────────────────────────────
  feature/time-machine-<id-1>             ✓ pushed
  feature/time-machine-<id-2>             ✗ not pushed
  feature/time-machine-<id-3>             ✗ not pushed
  feature/time-machine-<id-4>             ↷ skipped
  ...

 You chose to push <N-pushed> of <N-done> branches.

 Don't forget to push the remaining branches when you're
 ready — since you preferred to handle that yourself,
 here are the commands:

<for each pushed: false feature, one line:>
   git push -u origin feature/time-machine-<id>

 Take your time — Spec Kit Time Machine has done its part. 🚀
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Context

Project: OrthoPlus Enterprise
Auto-generated from: .kimi/skills/speckit-time-machine-next/SKILL.md
Synced: 2026-05-24T21:37:05-03:00

# speckit.time.machine.next ## Description ## Instructions --- name: speckit-time-machine-next description: Run the full SDD workflow for every pending feature in the Time Machine queue, sequentially compatibility: Requires spec-kit project structure with .specify/ directory metadata: author: github-spec-kit source: time-machine:commands/next.md --- # Time Machine — Next Feature Process every pending feature in the queue **one after the other** without stopping between them. For each feature the full spec-kit SDD lifecycle runs: **specify → clarify → plan → tasks → implement**. After each implementation the user is asked whether to push the branch. Declining does **not** stop the loop — the next feature starts immediately. A final summary is shown when all features are done. ## User Input {{arguments}} Accepted flags: - `--feature <id>` — start (or resume) from a specific feature instead of the next pending one - `--from <phase>` — when used with `--feature`, resume that feature from a specific phase (`specify`, `clarify`, `plan`, `tasks`, `implement`) - `--include-skipped` — re-run all previously skipped features after any remaining pending ones - `--redo <id>` — force re-run a specific feature regardless of its current status (`pending`, `in-progress`, `done`, or `skipped`) --- ## Steps > **This command runs a loop.** Repeat Steps 1–10 for every remaining > `pending` feature in order. Do not stop between features. Only exit the > loop when all eligible features are `done` or `skipped`, then proceed to Step 11. > When `--include-skipped` is passed, `skipped` features are included in the run. > When `--redo <id>` is passed, only that single feature is processed regardless of status. --- ### 1. Load and validate the queue Read `.specify/extensions/time-machine/features-queue.yml`. - If the file does not exist → stop and tell the user: `"No queue found. Run /speckit.time-machine.analyze first."` - **If `--redo <id>` was passed:** - Find the feature with that id regardless of its current status. - If not found → stop: `"No feature with id '<id>' found in the queue."` - Reset it: `status: pending`, clear `completed_at`, `branch`, `pushed`, `started_at`. - The loop runs for **only this one feature**. - **Otherwise:** - Collect every feature where `status` is `pending` or `in-progress`, in order. - For any collected feature where `status` is `in-progress` and `current_phase` is set, automatically treat it as if `--from <current_phase>` was passed for that feature. Print: `"Resuming '<Feature Name>' from phase: <current_phase>"` - If `--include-skipped` was also passed, append every `skipped` feature (in original order) and reset each to `status: pending`. - If `--feature <id>` was passed → start the loop from that feature only (skip any features before it in the collected list). - If no eligible features remain → skip straight to Step 11. --- ### 2. Mark as in-progress For the current feature, update `features-queue.yml`: ```yaml status: in-progress started_at: "<current ISO 8601 timestamp>" # only if not already set ``` Print: ``` ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Time Machine — Feature <#N of total> ID: <feature-id> Name: <Feature Name> Files: <comma-separated list> ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ ``` --- ### 3. Create a git branch ```bash git checkout -b feature/time-machine-<feature-id> ``` - If the branch already exists (resuming), run `git checkout feature/time-machine-<feature-id>` instead. - Update `features-queue.yml` → `branch: "feature/time-machine-<feature-id>"`. - If git is not initialised, warn the user and continue without branching. --- ### 4. Phase: Specify ``` [Phase 1/5] Specify — "<Feature Name>" ``` Update `features-queue.yml` → `current_phase: specify`. Run `/speckit.specify` scoped to this feature, passing: > "Feature: <Feature Name>. Description: <feature description>. > Relevant files: <comma-separated file list>. > Focus on this feature only; do not modify other features." Wait for the spec to be written before continuing. If `--from` is set to a later phase, skip this step. --- ### 5. Phase: Clarify ``` [Phase 2/5] Clarify — "<Feature Name>" ``` Update `features-queue.yml` → `current_phase: clarify`. Run `/speckit.clarify` for this feature. **Human gate:** present every generated question to the user and wait for answers before proceeding. Do not auto-answer or skip. If `--from` is set to a later phase, skip this step. --- ### 6. Phase: Plan ``` [Phase 3/5] Plan — "<Feature Name>" ``` Update `features-queue.yml` → `current_phase: plan`. Run `/speckit.plan` for this feature. Wait for the plan to be written. If `--from` is set to a later phase, skip this step. --- ### 7. Phase: Tasks ``` [Phase 4/5] Tasks — "<Feature Name>" ``` Update `features-queue.yml` → `current_phase: tasks`. Run `/speckit.tasks` for this feature. Wait for tasks to be generated. If `--from` is set to a later phase, skip this step. --- ### 8. Phase: Implement ``` [Phase 5/5] Implement — "<Feature Name>" ``` Update `features-queue.yml` → `current_phase: implement`. Run `/speckit.implement` for this feature. Wait for implementation to complete. --- ### 9. Satisfaction gate ``` ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Feature "<Feature Name>" implemented. Satisfied with the result? yes — continue to the next feature redo — re-run from a specific phase skip — skip this feature and move on wrap up — mark done, commit, and stop for now ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ ``` - **yes** → proceed to Step 10. - **redo** → ask `"Which phase? [specify / clarify / plan / tasks / implement]"` then loop back to the relevant step above. - **skip** → update `status: skipped`, `completed_at: <now>`, `pushed: null`, `current_phase: null`. Print a one-line skip notice then **continue immediately to the next feature** (go back to Step 2 with the next pending feature). - **wrap up** → mark the feature complete, commit all changes on the current branch, then stop: 1. Run `git add -A && git commit -m "feat(time-machine): complete <feature-id>"`. 2. Update `features-queue.yml`: `status: done`, `completed_at: <now>`, `current_phase: null`, `pushed: false`. 3. Print: ``` Feature "<Feature Name>" marked complete and committed. Run /speckit.time-machine.next to continue with the next feature. ``` 4. Exit the loop. Do **not** proceed to Step 10 or 11. --- ### 10. Push gate Ask the user: ``` Push branch "feature/time-machine-<feature-id>" to remote? [yes / no] ``` **If yes:** - Run `git push -u origin feature/time-machine-<feature-id>`. - Update `features-queue.yml`: `pushed: true`. - Print a one-line confirmation. **If no:** - Update `features-queue.yml`: `pushed: false`. - Print nothing extra — **immediately continue to the next feature**. Either way, update the feature: ```yaml status: done completed_at: "<current ISO 8601 timestamp>" current_phase: null ``` Then go back to Step 2 with the next pending feature. --- ### 11. All features done — final report Reached when every eligible feature is `done` or `skipped`. - If `--redo <id>` was used, "eligible" means just that one feature. - If `--include-skipped` was used, previously skipped features that were re-run now count toward `done`/`pushed`. Collect all features where `pushed: false` (declined) and `status: done`. **If every done feature was pushed (`pushed: true` or `pushed: null` for skipped):** ``` ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Time Machine complete! 🎉 All <N> features have been specced and implemented. ✓ Pushed: <N> ↷ Skipped: <N> ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ ``` **If any done features were NOT pushed (`pushed: false`):** ``` ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Time Machine complete! Here's a summary of all branches created: Branch Status ────────────────────────────────────────────────────── feature/time-machine-<id-1> ✓ pushed feature/time-machine-<id-2> ✗ not pushed feature/time-machine-<id-3> ✗ not pushed feature/time-machine-<id-4> ↷ skipped ... You chose to push <N-pushed> of <N-done> branches. Don't forget to push the remaining branches when you're ready — since you preferred to handle that yourself, here are the commands: <for each pushed: false feature, one line:> git push -u origin feature/time-machine-<id> Take your time — Spec Kit Time Machine has done its part. 🚀 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ ``` ## Context - Project: OrthoPlus Enterprise - Auto-generated from: .kimi/skills/speckit-time-machine-next/SKILL.md - Synced: 2026-05-24T21:37:05-03:00

{ "prompt": "# speckit.time.machine.next\n\n## Description\n\n\n## Instructions\n\n---\nname: speckit-time-machine-next\ndescription: Run the full SDD workflow for every pending feature in the Time Machine\n queue, sequentially\ncompatibility: Requires spec-kit project structure with .specify/ directory\nmetadata:\n author: github-spec-kit\n source: time-machine:commands/next.md\n---\n\n# Time Machine — Next Feature\n\nProcess every pending feature in the queue **one after the other** without\nstopping between them. For each feature the full spec-kit SDD lifecycle runs:\n**specify → clarify → plan → tasks → implement**. After each implementation\nthe user is asked whether to push the branch. Declining does **not** stop the\nloop — the next feature starts immediately. A final summary is shown when all\nfeatures are done.\n\n## User Input\n\n{{arguments}}\n\nAccepted flags:\n\n- `--feature <id>` — start (or resume) from a specific feature instead of the next pending one\n- `--from <phase>` — when used with `--feature`, resume that feature from a specific phase (`specify`, `clarify`, `plan`, `tasks`, `implement`)\n- `--include-skipped` — re-run all previously skipped features after any remaining pending ones\n- `--redo <id>` — force re-run a specific feature regardless of its current status (`pending`, `in-progress`, `done`, or `skipped`)\n\n---\n\n## Steps\n\n> **This command runs a loop.** Repeat Steps 1–10 for every remaining\n> `pending` feature in order. Do not stop between features. Only exit the\n> loop when all eligible features are `done` or `skipped`, then proceed to Step 11.\n> When `--include-skipped` is passed, `skipped` features are included in the run.\n> When `--redo <id>` is passed, only that single feature is processed regardless of status.\n\n---\n\n### 1. Load and validate the queue\n\nRead `.specify/extensions/time-machine/features-queue.yml`.\n\n- If the file does not exist → stop and tell the user:\n `\"No queue found. Run /speckit.time-machine.analyze first.\"`\n- **If `--redo <id>` was passed:**\n - Find the feature with that id regardless of its current status.\n - If not found → stop: `\"No feature with id '<id>' found in the queue.\"`\n - Reset it: `status: pending`, clear `completed_at`, `branch`, `pushed`, `started_at`.\n - The loop runs for **only this one feature**.\n- **Otherwise:**\n - Collect every feature where `status` is `pending` or `in-progress`, in order.\n - For any collected feature where `status` is `in-progress` and `current_phase` is set,\n automatically treat it as if `--from <current_phase>` was passed for that feature.\n Print: `\"Resuming '<Feature Name>' from phase: <current_phase>\"`\n - If `--include-skipped` was also passed, append every `skipped` feature (in original order) and reset each to `status: pending`.\n - If `--feature <id>` was passed → start the loop from that feature only\n (skip any features before it in the collected list).\n - If no eligible features remain → skip straight to Step 11.\n\n---\n\n### 2. Mark as in-progress\n\nFor the current feature, update `features-queue.yml`:\n\n```yaml\nstatus: in-progress\nstarted_at: \"<current ISO 8601 timestamp>\" # only if not already set\n```\n\nPrint:\n\n```\n━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━\nTime Machine — Feature <#N of total>\n ID: <feature-id>\n Name: <Feature Name>\n Files: <comma-separated list>\n━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━\n```\n\n---\n\n### 3. Create a git branch\n\n```bash\ngit checkout -b feature/time-machine-<feature-id>\n```\n\n- If the branch already exists (resuming), run `git checkout feature/time-machine-<feature-id>` instead.\n- Update `features-queue.yml` → `branch: \"feature/time-machine-<feature-id>\"`.\n- If git is not initialised, warn the user and continue without branching.\n\n---\n\n### 4. Phase: Specify\n\n```\n[Phase 1/5] Specify — \"<Feature Name>\"\n```\n\nUpdate `features-queue.yml` → `current_phase: specify`.\n\nRun `/speckit.specify` scoped to this feature, passing:\n\n> \"Feature: <Feature Name>. Description: <feature description>.\n> Relevant files: <comma-separated file list>.\n> Focus on this feature only; do not modify other features.\"\n\nWait for the spec to be written before continuing.\nIf `--from` is set to a later phase, skip this step.\n\n---\n\n### 5. Phase: Clarify\n\n```\n[Phase 2/5] Clarify — \"<Feature Name>\"\n```\n\nUpdate `features-queue.yml` → `current_phase: clarify`.\n\nRun `/speckit.clarify` for this feature.\n\n**Human gate:** present every generated question to the user and wait for\nanswers before proceeding. Do not auto-answer or skip.\n\nIf `--from` is set to a later phase, skip this step.\n\n---\n\n### 6. Phase: Plan\n\n```\n[Phase 3/5] Plan — \"<Feature Name>\"\n```\n\nUpdate `features-queue.yml` → `current_phase: plan`.\n\nRun `/speckit.plan` for this feature. Wait for the plan to be written.\nIf `--from` is set to a later phase, skip this step.\n\n---\n\n### 7. Phase: Tasks\n\n```\n[Phase 4/5] Tasks — \"<Feature Name>\"\n```\n\nUpdate `features-queue.yml` → `current_phase: tasks`.\n\nRun `/speckit.tasks` for this feature. Wait for tasks to be generated.\nIf `--from` is set to a later phase, skip this step.\n\n---\n\n### 8. Phase: Implement\n\n```\n[Phase 5/5] Implement — \"<Feature Name>\"\n```\n\nUpdate `features-queue.yml` → `current_phase: implement`.\n\nRun `/speckit.implement` for this feature. Wait for implementation to complete.\n\n---\n\n### 9. Satisfaction gate\n\n```\n━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━\nFeature \"<Feature Name>\" implemented.\n\nSatisfied with the result?\n yes — continue to the next feature\n redo — re-run from a specific phase\n skip — skip this feature and move on\n wrap up — mark done, commit, and stop for now\n━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━\n```\n\n- **yes** → proceed to Step 10.\n- **redo** → ask `\"Which phase? [specify / clarify / plan / tasks / implement]\"`\n then loop back to the relevant step above.\n- **skip** → update `status: skipped`, `completed_at: <now>`, `pushed: null`, `current_phase: null`.\n Print a one-line skip notice then **continue immediately to the next feature**\n (go back to Step 2 with the next pending feature).\n- **wrap up** → mark the feature complete, commit all changes on the current branch, then stop:\n 1. Run `git add -A && git commit -m \"feat(time-machine): complete <feature-id>\"`.\n 2. Update `features-queue.yml`: `status: done`, `completed_at: <now>`, `current_phase: null`, `pushed: false`.\n 3. Print:\n ```\n Feature \"<Feature Name>\" marked complete and committed.\n Run /speckit.time-machine.next to continue with the next feature.\n ```\n 4. Exit the loop. Do **not** proceed to Step 10 or 11.\n\n---\n\n### 10. Push gate\n\nAsk the user:\n\n```\nPush branch \"feature/time-machine-<feature-id>\" to remote? [yes / no]\n```\n\n**If yes:**\n\n- Run `git push -u origin feature/time-machine-<feature-id>`.\n- Update `features-queue.yml`: `pushed: true`.\n- Print a one-line confirmation.\n\n**If no:**\n\n- Update `features-queue.yml`: `pushed: false`.\n- Print nothing extra — **immediately continue to the next feature**.\n\nEither way, update the feature:\n\n```yaml\nstatus: done\ncompleted_at: \"<current ISO 8601 timestamp>\"\ncurrent_phase: null\n```\n\nThen go back to Step 2 with the next pending feature.\n\n---\n\n### 11. All features done — final report\n\nReached when every eligible feature is `done` or `skipped`.\n\n- If `--redo <id>` was used, \"eligible\" means just that one feature.\n- If `--include-skipped` was used, previously skipped features that were re-run now count toward `done`/`pushed`.\n\nCollect all features where `pushed: false` (declined) and `status: done`.\n\n**If every done feature was pushed (`pushed: true` or `pushed: null` for skipped):**\n\n```\n━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━\n Time Machine complete! 🎉\n\n All <N> features have been specced and implemented.\n\n ✓ Pushed: <N>\n ↷ Skipped: <N>\n━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━\n```\n\n**If any done features were NOT pushed (`pushed: false`):**\n\n```\n━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━\n Time Machine complete!\n\n Here's a summary of all branches created:\n\n Branch Status\n ──────────────────────────────────────────────────────\n feature/time-machine-<id-1> ✓ pushed\n feature/time-machine-<id-2> ✗ not pushed\n feature/time-machine-<id-3> ✗ not pushed\n feature/time-machine-<id-4> ↷ skipped\n ...\n\n You chose to push <N-pushed> of <N-done> branches.\n\n Don't forget to push the remaining branches when you're\n ready — since you preferred to handle that yourself,\n here are the commands:\n\n<for each pushed: false feature, one line:>\n git push -u origin feature/time-machine-<id>\n\n Take your time — Spec Kit Time Machine has done its part. 🚀\n━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━\n```\n\n## Context\n- Project: OrthoPlus Enterprise\n- Auto-generated from: .kimi/skills/speckit-time-machine-next/SKILL.md\n- Synced: 2026-05-24T21:37:05-03:00", "variables": [ "arguments" ], "notes": "Process every pending feature in the queue **one after the other** without stopping between them. For each feature the full spec-kit SDD lifecycle runs: **specify → clarify → plan → tasks → implement**. After each implementation the user is asked whether to push the branch. Declining does **not** stop the loop — the next feature starts immediately. A final summary is shown when all features are done.", "metadata": { "source": { "provider": "github-prompts", "repository": "https://github.com/B0yZ4kr14/OrthoPlus-Enterprise", "path": ".github/prompts/speckit.time.machine.next.prompt.md", "ref": "aa750bf474a8311bb48471c2d4d4baca8667e9b1", "url": "https://github.com/B0yZ4kr14/OrthoPlus-Enterprise/blob/aa750bf474a8311bb48471c2d4d4baca8667e9b1/.github/prompts/speckit.time.machine.next.prompt.md", "key": "B0yZ4kr14/OrthoPlus-Enterprise/.github/prompts/speckit.time.machine.next.prompt.md" } } }

speckit.time.machine.next

About

speckit.time.machine.next

Description

Instructions

name: speckit-time-machine-next description: Run the full SDD workflow for every pending feature in the Time Machine queue, sequentially compatibility: Requires spec-kit project structure with .specify/ directory metadata: author: github-spec-kit source: time-machine:commands/next.md

Time Machine — Next Feature

User Input

Steps

1. Load and validate the queue

2. Mark as in-progress

3. Create a git branch

4. Phase: Specify

5. Phase: Clarify

6. Phase: Plan

7. Phase: Tasks

8. Phase: Implement

9. Satisfaction gate

10. Push gate

11. All features done — final report

Context

Use it

Manifest

Reviews