Issync Plugins
Install issue-driven development commands for Claude Code—planning, progress documents, sub-issues, and completion rituals aligned with GitHub-style work tracking.
Overview
issync-plugins is a plugin marketplace for the Build phase that provides the issync plugin with issue-driven slash commands for planning, progress docs, and sub-issue lifecycle.
What is this marketplace?
- Single issync plugin with issue-driven development tooling
- Documented commands: /plan, /compact-progress-document, /create-sub-issue, /complete-sub-issue, /understand-progress
- Japanese product description: 論点駆動開発 (issue-driven development)
- Source path: ./.claude-plugins/issync under MH4GF owner
- Process-oriented Claude Code plugin, not a hosted monitoring service
- Marketplace bundles 1 plugin: issync
- Five named slash workflows advertised in marketplace metadata
Community signal: 3 GitHub stars.
What problem does it solve?
When issues and agent chat diverge, solo builders lose track of sub-scope, progress narratives, and what still blocks shipment.
Who is it for?
Claude Code users who already track work in issues and want slash-command rituals for plan → sub-issue → progress → complete loops.
Skip if: Teams that need full Jira-style PM SaaS, plugins without issue-based workflow, or English-only UX when you cannot read the Japanese positioning text.
What do I get? / Deliverables
After you add the marketplace, Claude Code can run issync commands to plan work, maintain compact progress documents, and manage sub-issues through completion.
- Registered issync-plugins marketplace with issync enabled
- Repeatable /plan, progress compaction, and sub-issue lifecycle invocations in Claude Code
Plugins in this marketplace
1 plugin — install individually after you add the marketplace.
Recommended Marketplaces
Journey fit
issync advertises slash workflows (/plan, progress compaction, sub-issue lifecycle, understanding progress) that keep implementation tied to issues—classic Build-phase PM discipline for solo shippers. PM is the canonical shelf because every listed command governs how work is planned, decomposed, documented, and closed—not frontend layout, tests, or launch SEO.
How it compares
Issue-driven PM command pack, not an LLM code-review bridge or infrastructure monitoring plugin.
Common Questions / FAQ
Who is Issync Plugins for?
It is for developers using Claude Code who organize work around issues and want structured /plan and sub-issue commands baked into the agent.
When should I use Issync Plugins?
Use it during Build when you are breaking epics into sub-issues, writing progress summaries, or closing loops before the next coding push.
How do I add Issync Plugins to my agent?
Register the MH4GF/issync marketplace in Claude Code and enable the issync plugin from ./.claude-plugins/issync.