Repository navigation
Home
Published from
docs/product-map.mdat150f808. Edit the source in the repository, not this page.
Sanduq Skills ships six skills in three bundles. Each bundle installs as one Claude Code plugin and has its own version.
Editable source: product-map.html. Still version: product-map.svg.
| Bundle | Version | Skills | What it is for |
|---|---|---|---|
illustration-tools |
3.7.1 | illustrate | Diagrams and charts as editable HTML, with SVG, PNG, animated SVG, and GIF export. |
dev-tools |
2.0.4 | user-manual and github-wiki-publish | Application manuals and standalone publishing of existing pages, reports, diagrams, and assets to a GitHub Wiki. |
agent-tools |
1.9.2 | delegate-task, progress-report and planning-majlis | Handing a task to another agent CLI and measuring what it did; keeping a live progress report of a plan or feature; planning software or a feature with a gated committee of expert roles. |
- illustrate draws 44 kinds of diagrams and charts in your project's theme.
- user-manual discovers your modules, writes the pages, and audits coverage. It also writes API references split by audience, release notes and migration guides, and redacted screenshots, and sets up private pull request previews. It assembles each edition as Markdown and renders it the way you choose: as Markdown, through your own templates and tools, or as an MkDocs site and PDF.
- delegate-task runs one task on another agent CLI, the harness, and reports a measured result.
- github-wiki-publish publishes supplied content to a GitHub Wiki, preserves unrelated pages and navigation, and verifies the remote commit and served page when authenticated browser access is available.
- progress-report keeps a live report of a Markdown plan or a Spec Kit feature: tasks, lanes, blockers, decisions, and what the Claude Code and Codex hooks observe. It is a projection, so no agent is spent on upkeep.
- planning-majlis plans new software or a feature with a committee of expert roles run as parallel subagents, and gates the plan: every seated role at 9/10 with no open blockers in the decision record.
- user-manual does its own API, release, screenshot and preview work. Since dev-tools 2.0 they are reference files inside the skill, loaded when a task needs them.
- user-manual uses illustrate when it is installed. Its rules say to generate diagrams with the illustrate skill when it is available, including ER diagrams for the data reference. Illustrate does not depend on user-manual.
-
delegate-task and progress-report stand alone. They fit together:
progress runscan read the runs that delegate-task writes to.delegate/runs, and a lane can name the harness and model you delegated to. - planning-majlis stands alone. It can use delegate-task, when installed, to run a critic on a different agent CLI or model from the authors.
-
github-wiki-publish stands alone. It accepts existing pages, reports, diagrams, and assets
without requiring
user-manualor Spec Kit. Write or generate the pages first, then publish them. - Every skill works on its own. None needs Spec Kit. You can install only the ones you need.
| You want to | Start with |
|---|---|
| Draw a diagram or chart | illustrate |
| Document an application | user-manual |
| Add API, release, screenshot, or preview work to a manual | user-manual |
| Publish existing pages, reports, diagrams, or assets to a repository Wiki | github-wiki-publish |
| Get a second agent to do or check a task | delegate-task |
| Watch progress on a plan or feature, and see which agent does what | progress-report |
| Plan new software or a feature with a committee of experts before building | planning-majlis |