💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐

@syedabdulaman173-lang rather than trying to find the plan document after it's generated, a more direct approach is to generate a plan within the project repository itself. My company just released an entire context management framework that is basically "plan mode" on steroids and works with files within your repository. This Jekt™ context architecture is free and open, and works across tool vendors.

https://jekt.dev/

Jekt surfaces and persists project semantics in the project repository itself: not only plans but designs, decisions, pivots, discoveries, etc. At the low level it manages plans as you were asking about in this discussion; at the top level it can even replace an entire ticket tracking system such as Jira. It provides interoperability tool conventions for semantic artifacts. Here is an example of a repository after working with Jekt:

.jekt/
└── tickets/
    └── auth-42/
        ├── description - Token Refresh.md      ← scope and intent
        ├── description.yaml                    ← status, kind, priority
        ├── minutes.md                          ← decisions and insights
        ├── plans/
        │   └── 2026-05-14-refresh-flow.md      ← implementation plan
        ├── designs/
        │   └── Token Expiration Model.md       ← durable reasoning
        ├── comments/
        │   └── 2026-05-14T18-22-00Z.md         ← discussion
        ├── summary.md                          ← what was accomplished
        └── todo - Rotate Signing Keys.md       ← deferred work

A VS Code extension is coming soon, and I'm reaching out to GitHub Copilot leaders so they can add native recognition of Jekt artifacts in GitHub Copilot itself. In the meantime you can try it out right now with the reference prompts.

I'd love to get your feedback on Jekt.