Sudocode Spec & Issue Management FAQs

Question 1

Can I manually edit the Sudocode tracking files?

Accepted Answer

Yes. While you can use MCP tools for structured updates, the system supports bidirectional sync. You can directly edit the Markdown files in the .sudocode/ directory to write detailed content or refactor descriptions, and Claude will recognize the changes.

Question 2

What does the Sudocode skill do for Claude Code?

Accepted Answer

Sudocode provides a lightweight agent orchestration system that lives directly in your repository. it allows Claude to manage technical requirements (specs) and actionable tasks (issues) using Markdown files, ensuring work context and progress persist across sessions.

Question 3

What are Obsidian-style mentions in this context?

Accepted Answer

Sudocode supports [[ID]] syntax (like [[s-123]]) within Markdown files. This allows you to link specs and issues inline, automatically creating bidirectional relationships and dependency links without needing to call separate management tools.

Question 4

When should I use a spec versus an issue?

Accepted Answer

Use specs to document high-level user intent, architectural designs, and feature requirements. Use issues for concrete, actionable work items that implement those specs. This separation keeps goals clear while tracking granular implementation progress.

Question 5

How does this skill improve my AI development workflow?

Accepted Answer

It eliminates context loss by storing plans in your repo. By using dependency graphs and the 'ready' tool, Claude can proactively identify unblocked tasks, follow a logical execution order, and document implementation gaps through structured feedback loops.

Sudocode Spec & Issue Management

Sudocode Spec & Issue Management

소개

주요 기능

사용 사례

소개

주요 기능

사용 사례