Video summary

Up & Running with GitHub Spec Kit #4 - The /clarify Command

Main summary

Key takeaways

Technology

Branch / spec setup (context)

  • A new spec file is created inside a specs/ folder under an initial page setup directory.
  • The spec is also used to switch work to a feature branch where all subsequent planning and code generation will occur.

Optional /clarify command (clarification stage)

After creating the spec, you can choose to:

  • Go straight to planning via a /plan command, or
  • Run /clarify first.

The /clarify command makes the coding agent:

  • read the current spec file,
  • detect ambiguities, edge cases, and underspecified areas,
  • ask the user targeted questions, and
  • update/bake the answers back into the spec.

It’s not required, but recommended—especially if the spec contains “needs clarification” markers.

Guided prompt Q&A (what the tutor chooses)

  1. App store goals data persistence across browser sessions

    • Chosen: Option A – local storage
    • Alternatives mentioned: session storage, cloud database, file download/upload, or short custom answer.

  2. When a goal’s end date has already passed

    • Chosen: Delete overdue goals
    • Alternatives included: overdue labels, moving to completed/expired, urgent warning popup, or separate overdue column.

  3. Submitting the goal form with empty fields

    • Chosen: Option A – simple inline error UI
    • (Red borders + inline errors were listed; the tutor selects the simpler “Option A” approach.)

  4. Ordering of completed goals (right column)

    • Chosen: Most recently completed at the top
    • Other options included: oldest first, alphabetical, or by completion date.

  5. Days remaining display far in the future

    • Chosen: Convert to approximate units rather than exact day counts
    • Options mentioned: exact number, cap maximum, show both formats.

Spec file updates + next step

  • After answering five clarification questions, the tool indicates clarifications are complete.
  • The tutor then notes that the spec file now has added sections:
    • functional requirements informed by the chosen answers
    • a record of the clarification Q&A entries
  • Recommendation shown: proceed to the plan stage (keeping the changes).

Main source / speakers

  • The tutorial narrator/instructor (“Okay then my friends…”) guiding the use of GitHub Spec Kit commands (/specify, /clarify, /plan).
  • The coding agent invoked by the /clarify command (the agent that reads the spec, asks questions, and updates the spec).

Original video