矛盾解消駆動開発のためのツール群: plan実行(/plan)、アーキテクチャ決定(/architecture-decision)、Open Question解消(/resolve-question)、Open Question追加(/add-question)、plan.md圧縮(/compact-plan)、タスクのサブissue化と順序管理(/create-sub-issue)、サブissue完了(/complete-sub-issue)
You can install this plugin from any of these themed marketplaces. Choose one, add it as a marketplace, then install the plugin.
Choose your preferred installation method below
A marketplace is a collection of plugins. Every plugin gets an auto-generated marketplace JSON for individual installation, plus inclusion in category and themed collections. Add a marketplace once (step 1), then install any plugin from it (step 2).
One-time setup for access to all plugins
When to use: If you plan to install multiple plugins now or later
Step 1: Add the marketplace (one-time)
/plugin marketplace add https://claudepluginhub.com/marketplaces/all.jsonRun this once to access all plugins
Step 2: Install this plugin
/plugin install contradiction-tools@allUse this plugin's auto-generated marketplace JSON for individual installation
When to use: If you only want to try this specific plugin
Step 1: Add this plugin's marketplace
/plugin marketplace add https://claudepluginhub.com/marketplaces/plugins/contradiction-tools.jsonStep 2: Install the plugin
/plugin install contradiction-tools@contradiction-toolsCLI tool to sync text between GitHub Issue comments and local files, enabling AI-driven development workflows.
issync allows AI agents to maintain living documentation (like plan.md) in GitHub Issues as a single source of truth. Multiple local sessions (git worktrees, Devin, Claude Code, etc.) can read and write to the same document concurrently without git conflicts.
Core Features:
npm install -g @mh4gf/issync
Requirements:
repo scopeexport GITHUB_TOKEN=$(gh auth token) # Using GitHub CLI
# or
export GITHUB_TOKEN=ghp_your_token_here
# Link a GitHub Issue to a local file
issync init https://github.com/owner/repo/issues/123 --file docs/plan.md
# Or create a new file from template
issync init https://github.com/owner/repo/issues/123 --file docs/plan.md --template template.md
⚠️ IMPORTANT: Always start watch mode BEFORE editing files
issync watch
# With custom polling interval (default: 60s)
issync watch --interval 10
AI agents and editors can now read/edit the file normally. issync automatically syncs changes.
issync init <issue-url>Initialize sync for a GitHub Issue.
issync init https://github.com/owner/repo/issues/123 --file docs/plan.md
Options:
--file <path>: Local file path (default: .issync/docs/plan-{issue-number}.md)
.issync/docs/plan-123.md--template <path>: Create file from template if it doesn't existBehavior:
issync pullPull remote changes from GitHub Issue comment to local file.
issync pull
issync pushPush local changes to GitHub Issue comment.
issync push
# Force push (skip optimistic lock check)
issync push --force
Options:
--force: Skip optimistic lock check and force overwrite remote changes
git push --forceExample workflow with force:
# 1. Check remote content first
issync pull
# 2. Review the changes
cat docs/plan.md
# 3. If local is correct and you want to overwrite remote
issync push --force
issync watchStart watch mode (foreground process, press Ctrl+C to stop).
issync watch
# Custom polling interval
issync watch --interval 10
Watch mode behavior:
chokidarissync stores state in .issync/state.yml (should be git-ignored):
issue_url: https://github.com/owner/repo/issues/123
comment_id: 123456789
local_file: docs/plan.md
last_synced_hash: abc123def
last_synced_at: '2025-10-14T12:00:00.000Z'
Add to .gitignore:
.issync/
Recommended workflow in CLAUDE.md or project documentation:
# 1. Set GitHub token
export GITHUB_TOKEN=$(gh auth token)
# 2. Start watch mode FIRST (before any edits)
issync watch
# 3. Then edit files
# AI agents can now safely read/edit the synced file
Why this order matters: The MVP's pull operation overwrites local files. If you edit before starting watch, and the remote is outdated, your changes may be lost.
issync uses invisible HTML comment markers to identify its managed comments in GitHub Issues:
<!-- issync:v1:start -->
# Your document content here
...
<!-- issync:v1:end -->
Benefits:
v1) enables future format upgradespush command restores themWhen issync pulls remote changes, it updates the local file. If an AI agent's Edit() tool tries to modify the file, it will fail because old_string no longer matches (the file was updated). The agent naturally re-reads and retries.
last_synced_hash from state with remote hashOn watch startup, issync performs a 3-way comparison:
See CLAUDE.md for development setup and architecture details.
# Install dependencies
bun install
# Run CLI in development
bun run dev init <issue-url>
# Run tests
bun test
# Build for distribution
bun run build
MIT
MH4GF
0.7.0