Docs
Every tool connects to the same address, https://tuskway.com/mcp. Sign in once. Where your tool has a plugin, one install brings the MCP server and the workflow skills. Agents without a browser use a token instead.
Set up your tool
- CursorSkills and MCP server
- Claude CodeSkills and MCP server
- CodexSkills and MCP server
- Copilot CLISkills and MCP server
- Grok BuildSkills and MCP server
- GrokMCP server
- Gemini CLISkills and MCP server
- OpenCodeSkills and MCP server
- PiSkills and MCP server
- VS CodeMCP server
- ChatGPTMCP server
- Le ChatMCP server
- Other clientsMCP server
- Cloud agents and CIMCP server with a token
The workflow
Four steps take a feature from idea to pull request. The plugin adds each one as a skill, and the server offers the same steps as MCP prompts.
/start-epicCapture the context
Tell your agent what you're building. It writes down the goal, the constraints and the open questions, so nobody has to explain them again.
/write-designAgree on the design
Your agent drafts the tech design in sections. Teammates comment on the lines that need work, and an agent works through every thread.
/draft-ticketsSplit it into tickets
Each brief has a goal, acceptance checks, dependencies and the files to touch. Publish them to GitHub Issues, GitLab, Linear or Jira.
/tackle-ticketBuild in parallel
Any agent on the team picks up a ticket, reads its brief and design section, and moves it to review when the pull request opens.
More
- Spec-driven development
Why a written spec makes agents useful on a team.
- Integrations
What each AI tool and issue tracker gets from Tuskway.
- Support
How to reach us and what to include in your message.