Speq code tools
A light-weight and straightforward system for spec-driven development with Claude Code or OpenAI Codex. Written in Rust π¦
npx -y skills add marconae/speq-skill --skill speq-code-toolsAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
What its author says it does
Copied from the file, not written here
Semantic code navigation and editing via Serena MCP β symbol-level tools preferred over grep/find/manual edits. Triggered by /speq-mission, /speq-implement, planner-agent, implementer-agent, implementer-expert-agent, code-reviewer, and recorder-agent.
SKILL.md
1.6 KB, as published. Nobody here has run it
Code Tools
Semantic code navigation and editing via Serena MCP.
Tool Preference
| Task | Use | Not |
|---|---|---|
| List directory | list_dir | ls, find |
| Find files | find_file | find, rg --files |
| File symbols | get_symbols_overview | rg "class|function" |
| Symbol definition | find_symbol | rg "function foo" |
| Symbol references | find_referencing_symbols | rg "foo(" |
| Update function | replace_symbol_body | read/edit/write |
| Insert after | insert_after_symbol | read/edit/write |
| Insert before | insert_before_symbol | read/edit/write |
| Rename symbol | rename_symbol | rg + manual edits |
Reflection Checkpoints
Apply the Feynman Technique β explain your understanding before proceeding. Call these tools at key moments:
| Tool | When |
|---|---|
think_about_collected_information | After exploration sequence |
think_about_task_adherence | Before writing code |
think_about_whether_you_are_done | Before reporting completion |
Workflow
Explore β find_symbol, get_symbols_overview
Understand β find_referencing_symbols
Reflect β think_about_collected_information
Edit β replace_symbol_body, insert_*_symbol
Verify β find_referencing_symbols
Complete β think_about_whether_you_are_done