claude

sig

Phase-0 + six-phase AI development workflow (CALIBRATE → DISCUSS → PLAN → EXECUTE → VERIFY → REVIEW → SHIP) with on-demand quality skills, specialized agents, anti-rationalization gates, and project-tier calibration. Slash-command prefix: /sig:* (Signal is the project brand; sig is the namespace). Integrates patterns from GSD, Agent Skills, and the broader Claude Code plugin ecosystem (gstack, pm-skills, superpowers, compound-engineering, planning-with-files, oh-my-claudecode).

1 on GitHubby InsightRiotv0.1.54MITupdated 3 days ago
/

Plugin sig from marketplace signal in insightriot/signal. Commands read from the repo's manifest — 3 days ago.

This plugin runs code on your machine — its hooks fire automatically on events like tool use. The exact commands are listed below; read them before installing.

What it installs

Skills (15)

  • idea-refine

    Refines ideas iteratively. Refine ideas through structured divergent and convergent thinking. Use "idea-refine" or "ideate" to trigger.

  • spec-driven-development

    Creates specs before coding. Use when starting a new project, feature, or significant change and no specification exists yet. Use when requirements are unclear, ambiguous, or only exist as a vague idea.

  • using-agent-skills

    Discovers and invokes agent skills. Use when starting a session or when you need to discover which skill applies to the current task. This is the meta-skill that governs how all other skills are discovered and invoked.

  • planning-and-task-breakdown

    Decomposes work into small, verifiable tasks with explicit acceptance criteria. Use when you have a spec and need to break it into implementable units, when a task feels too large or vague to start, or when work needs to be parallelized.

  • code-review-and-quality

    Multi-dimensional code review with quality gates. Use before merging any PR or change, after completing a feature implementation, when another agent or model produced code you need to evaluate, when refactoring existing code, or after any bug fix.

  • code-simplification

    Simplifies code for clarity. Use when refactoring code for clarity without changing behavior. Use when code works but is harder to read, maintain, or extend than it should be. Use when reviewing code that has accumulated unnecessary complexity.

  • performance-optimization

    Optimizes application performance. Use when performance requirements exist, when you suspect performance regressions, or when Core Web Vitals or load times need improvement. Use when profiling reveals bottlenecks that need fixing.

  • security-and-hardening

    Security-first development practices. Use when building anything that accepts user input, implementing authentication or authorization, storing or transmitting sensitive data, integrating with external APIs, adding file uploads or webhooks, or handling payment or PII data.

  • ci-cd-and-automation

    Automates CI/CD pipeline setup. Use when setting up or modifying build and deployment pipelines. Use when you need to automate quality gates, configure test runners in CI, or establish deployment strategies.

  • deprecation-and-migration

    Structured code removal and migration. Use when replacing old systems, sunsetting features, consolidating duplicates, removing dead code, or planning the lifecycle of new systems. Covers the deprecation decision, migration patterns, and zombie code.

  • documentation-and-adrs

    Document decisions, not just code. Use when making architectural decisions, choosing between approaches, adding or changing APIs, shipping user-facing features, onboarding team members, or when you find yourself explaining the same thing repeatedly.

  • git-workflow-and-versioning

    Atomic commits, clean history, and disciplined branching. Use for every code change. Covers commit conventions, branching strategy, worktrees for parallel work, pre-commit hygiene, and using git for debugging.

  • shipping-and-launch

    Ship with confidence. Use when deploying features to production, releasing significant changes, migrating data or infrastructure, opening beta programs, or any deployment that carries risk. Covers pre-launch checklists, feature flags, staged rollouts, monitoring, and rollback strategies.

  • browser-testing-with-devtools

    Chrome DevTools MCP for runtime verification. Use when building or modifying anything that renders in a browser. Use when you need to verify that a fix actually works in the browser, debug layout issues, diagnose console errors, or analyze API requests.

  • debugging-and-error-recovery

    Systematic debugging with structured triage. Use when tests fail, builds break, runtime behavior doesn't match expectations, or a bug report arrives. Covers test failures, build errors, runtime bugs, and production incidents.

Slash commands (20)

  • /sig:add

    Capture-and-route new work — appends a stamped entry to .planning/ISSUES-INBOX.md (default; falls back to the legacy FUTURE-IDEAS.md name if that is what the repo still has) after verbatim capture, sensitive-data scrub, and atomic write. Route explicitly with --question (OPEN-QUESTIONS.md), --bug (B

  • /sig:advise

    Review this project's own .planning/ docs for the big picture, propose 3–5 priorities — every claim carrying a citation that resolves — and ask which to work on. Records the pick in its dated advisory and offers to start it. Read-only except for that advisory. Not phase-gated.

  • /sig:calibrate

    Phase 0 — classify project into SKETCH / FEATURE / SPIKE / FULL and write .planning/PROFILE.md to drive downstream rigor.

  • /sig:discuss

    DISCUSS phase — gather implementation decisions through adaptive questioning before planning. Loads idea-refine and spec-driven-development skills.

  • /sig:docs-archive

    File finished work out of the live .planning/ root into .planning/archive/. Only units that are genuinely closed move; every other unit is reported with the reason it was declined. Dry-run by default; --apply writes. Not phase-gated.

  • /sig:docs-index

    Regenerate .planning/INDEX.md — the auto-generated documentation map. Walks the corpus, renders mechanical rows (path · growth-policy), re-attaches curated notes by key, and writes only when the content changed. Idempotent; not phase-gated.

  • /sig:docs-migrate

    Auto-sensing doc-runtime migrate — reorganizes THIS project's .planning/ docs to the current layout (de-prose frontmatter, relocate bloated bodies, evict closed-Epic narrative, build the archive tree; and on a v2→v3 layout bump: rename FUTURE-IDEAS→ISSUES-INBOX, create BACKLOG, evict closed-mileston

  • /sig:docs-sweep

    Read-only doc-hygiene sweep over the invoking project — dead internal links, unfilled [FILL IN] stubs, INDEX/roster/version drift, a stale capture inbox, and CLAUDE.md bloat. Detect-and-report only, with one exception: on a v2 work store it confirms fixed closes whose commit is on the default branch

  • /sig:drive

    Run the phase flow without sitting at every gate. Reads the attention setting, advances while it may, and stops the moment a decision genuinely needs you — with the reason named. Queues what it can defer. Never merges.

  • /sig:escalate

    Adjust tier mid-flight, UP OR DOWN. Re-runs calibration carrying current context, updates PROFILE.md (the active Epic's, if one is open), and appends to escalation_history. Use when scope or stakes grow — and equally when the work turns out smaller than the project's ceiling (de-escalation; no back-

  • /sig:execute

    EXECUTE phase — build the plan's tasks wave by wave, tests first where required, one commit each.

  • /sig:init

    Brownfield onboarding — bring Signal to an existing codebase. Scans the repo, writes .planning/LANDSCAPE.md, drafts a baseline PROJECT.md, then hands off to /sig:calibrate.

  • /sig:item

    Change work items in the work store — new, triage, move, close, reopen, edit, show, list, and confirm a close by hand where git never can. Every change to an item goes through this command as an event on its record, so an item's status is always derived from its own history. Only for projects with t

  • /sig:new-project

    Initialize a new project with the Signal workflow. Creates .planning/ directory, PROJECT.md, and kicks off the CALIBRATE phase.

  • /sig:plan

    PLAN phase — research, a plan in vertical slices with acceptance criteria, plan validation, and a test for every criterion.

  • /sig:resume

    Resume work on a Signal project. Reads PROFILE.md + STATE.md + the current phase's artifact, prints a re-orientation, and asks if you're ready to continue.

  • /sig:review

    REVIEW phase — review the built change for quality, security, performance and simplicity, have fresh-context agents read it, fix what they find, and record a verdict.

  • /sig:ship

    SHIP phase — check the change is ready, open the pull request, record the phase and close the work in the project's records, in one commit.

  • /sig:status

    Read-only project inspection — synthesizes PROFILE.md + STATE.md (and OPEN-QUESTIONS.md if present) into a one-screen status report with tier-aware next-action guidance.

  • /sig:verify

    VERIFY phase — check the built work against its acceptance criteria and requirements, run the suite and build, and write a report that states its totals.

Hooks (10)

  • SessionStart

    bash ${CLAUDE_PLUGIN_ROOT}/hooks/session-start.sh

  • SessionStart

    node ${CLAUDE_PLUGIN_ROOT}/hooks/warn-dirty-execute.js

  • SessionStart

    node ${CLAUDE_PLUGIN_ROOT}/hooks/warn-layout-drift.js

  • SessionStart

    node ${CLAUDE_PLUGIN_ROOT}/hooks/warn-stale-plugin-binding.js

  • PreToolUse

    node ${CLAUDE_PLUGIN_ROOT}/hooks/check-state-write.js

  • PreToolUse

    node ${CLAUDE_PLUGIN_ROOT}/hooks/check-commit-test-run.js

  • PostToolUse

    node ${CLAUDE_PLUGIN_ROOT}/hooks/record-ask.js

  • Stop

    node ${CLAUDE_PLUGIN_ROOT}/hooks/keep-executing.js

  • Stop

    node ${CLAUDE_PLUGIN_ROOT}/hooks/check-limits-filed.js

  • UserPromptSubmit

    node ${CLAUDE_PLUGIN_ROOT}/hooks/show-open-items.js

View source on GitHub signal-map-two.vercel.app

Maintain sig?

This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.

claude & codex pluginslisted