Skip to content

Debug workflow #1529

Closed
Closed

Description

@c30ra

What is the supposed workflow to debug/fix code added after /implement? To keep context low, I start a new session after each "/" command. It would be usefull to have a /speckit-debug command. This way i have already the specifications set for the current "specify", and the model have enoght context to work with, without rescan the working directory

Activity

  1. Kataki-Takanashi commented on Jan 27, 2026

    @Kataki-Takanashi

    What is the supposed workflow to debug/fix code added after /implement? To keep context low, I start a new session after each "/" command. It would be usefull to have a /speckit-debug command. This way i have already the specifications set for the current "specify", and the model have enoght context to work with, without rescan the working directory

    Please see/support #442

  2. mnriem commented on Feb 4, 2026

    @mnriem
    Collaborator

    As this is a question I am moving it to discussions so our community can weigh in

  3. locked and limited conversation to collaborators on Feb 4, 2026
  4. converted this issue into a discussion #1564 on Feb 4, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions