You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It seems we would use MarkDown for preview. So as we move through the flow, /specify > /plan > /tasks ... we have all these MarkDown docs, that do not properly preview in VSCode as the content is held in a mdc code block. This makes the doc not preview friendly.
One of the goals here is to practice good project workflow. If the artifacts are harder to read, the number of devs who actually take time to read will be lower.
This issue has been automatically marked as stale because it has not had any activity for 150 days. It will be closed in 30 days if no further activity occurs.
This issue has been automatically marked as stale because it has had no activity for 60 days. It will be closed in 30 days unless there is a substantive update. If the problem still applies, please provide updated context such as whether it is still reproducible, the affected version or environment, its current impact, and any new reproduction details. A comment that only states that the issue is "still relevant" does not give maintainers enough information to reconsider it.
Activity
bkowshik commentedon Mar 10, 2026
+1
Instead of an extention, I think we should have this as part of the
spec-kitproject itself.Example
Below is how the Markdown looks like in
codemode.And, below is how it looks in
previewmode.mnriem commentedon Mar 10, 2026
@sosensible @bkowshik Feel free to create a PR for this :)
github-actions commentedon Aug 8, 2026
This issue has been automatically marked as stale because it has not had any activity for 150 days. It will be closed in 30 days if no further activity occurs.
anetrebskii commentedon Aug 8, 2026
Why not to use markdown editors like https://notula.org/ or https://obsidian.md/?
github-actions commentedon Oct 8, 2026
This issue has been automatically marked as stale because it has had no activity for 60 days. It will be closed in 30 days unless there is a substantive update. If the problem still applies, please provide updated context such as whether it is still reproducible, the affected version or environment, its current impact, and any new reproduction details. A comment that only states that the issue is "still relevant" does not give maintainers enough information to reconsider it.