MichaelYcJo

MichaelYcJo/SpecSeal

Plugin Claude Code

SpecSeal — specs, sealed: implement/review agent chain, evidence ledger with drift detection, hook-enforced gates.

MichaelYcJo/SpecSeal

Plugin Claude Code

SpecSeal — specs, sealed: an implement/review agent chain with hook enforcement, an evidence ledger with drift detection, and a tool-agnostic review handoff protocol.

MichaelYcJo/SpecSeal

Instructions file

Claude Code instructions for MichaelYcJo/SpecSeal, covering tooling, safety, session cost, git and repo rule — no real identifiers in examples or fixtures.

MichaelYcJo/SpecSeal

Agent

Migration fact-finder. Spawn only in projects with a migration config (.specseal/parity.md) to establish what the original code actually does — facts with coordinates, no verdicts. Called by smith during implementation and by the review orchestrator during parity review.

MichaelYcJo/SpecSeal

Agent

Implementation agent. Spawn for feature work, ticket implementation, refactors, and incorporating review feedback. Follows the implement skill (SDD procedure, three-axis document layout); hands finished work to the review chain.

MichaelYcJo/SpecSeal

Agent

Review agent. Spawn to review a PR, diff, or branch — spec compliance first, then quality. Reads earlier review rounds and inherits their verdicts; returns a report for the orchestrator to verify and post.

MichaelYcJo/SpecSeal

Hook

Runs before the agent uses a tool for Bash, Agent, Task and Skill tool calls, executing dispatch.py via python3 (3 commands). From MichaelYcJo/SpecSeal.

MichaelYcJo/SpecSeal

Hook

Runs after a tool call finishes for Bash, Write, Edit and NotebookEdit tool calls, executing dispatch.py via python3 (2 commands). From MichaelYcJo/SpecSeal.

MichaelYcJo/SpecSeal

Hook

Runs when a session starts, executing dispatch.py via python3. From MichaelYcJo/SpecSeal.

MichaelYcJo/SpecSeal

Skill Claude CodeCodex

Validate project-specific rules a linter cannot express, declared as .claude/audit-rules/.md. Use when: checking conventions this repo wrote down for itself before a commit or release. NOT for: formatting or style a linter already enforces, security review (security-audit), or comparing a spec against the code…

MichaelYcJo/SpecSeal

Skill Claude CodeCodex

Resolve build, compile, and type-check errors at their cause instead of suppressing them. Use when: the build does not produce output — type errors, missing modules, syntax or config failures. NOT for: code that compiles but behaves wrong (that is debug).

MichaelYcJo/SpecSeal

Skill Claude CodeCodex

Establish a rollback point before an operation that is hard to undo, and get explicit approval with the blast radius stated. Use when: deleting files, migrating schemas, renaming across the codebase, or changing a core abstraction — where reverting later is not just a git command. NOT for: ordinary refactors that a…

MichaelYcJo/SpecSeal

Skill Claude CodeCodex

Two-stage review methodology (spec compliance, then quality) with comparison axes, cross-session review records, and re-review inheritance. Use when: reviewing a PR or diff, re-reviewing after fixes, orchestrating reviewer agents. NOT for: implementing fixes (use implement), style-only linting a formatter can do, or a…

MichaelYcJo/SpecSeal

Skill Claude CodeCodex

Readiness check before implementing: does something equivalent already exist, is the API verified against the installed version, is the cause of the bug actually understood rather than guessed. Reports which checks are unsatisfied — no score, since any single miss is the whole answer. Use when: about to build…

MichaelYcJo/SpecSeal

Skill Claude CodeCodex

Find the cause of wrong behavior: reproduce, locate, one hypothesis at a time, then a failing test before the fix. Use when: the code runs but produces the wrong result, or a test fails. NOT for: build, compile, or type-check errors — nothing runs there, so there is nothing to reproduce (that is build-fix).

MichaelYcJo/SpecSeal

Skill Claude CodeCodex

Verify that the evidence ledger's spec-to-code coordinates still resolve — broken links fail, ranges touched since the baseline demand re-verification. Use when: checking ledger health, before merging spec-driven work, wiring the check into CI, or after large refactors. NOT for: judging whether the code is CORRECT …

MichaelYcJo/SpecSeal

Skill Claude CodeCodex

Wire the ledger drift check into this repo's CI — vendor the checker and write the workflow, so drift fails a build instead of waiting to be run by hand.

MichaelYcJo/SpecSeal

Skill Claude CodeCodex

Decompose work into ordered tasks with dependencies mapped, then lock scope in writing before starting. Use when: the work spans more than about three files or needs phasing, and no plan exists yet. NOT for: firing on your own while the smith is driving — its design gate invokes this when decomposition is what the…

MichaelYcJo/SpecSeal

Skill Claude CodeCodex

Compare a design or spec document against what was actually built — API surface, data model, business logic — and list what is missing, extra, or divergent. Use when: a written design exists and someone needs to know how far the implementation has drifted from it. NOT for: checking that ledger coordinates still…

MichaelYcJo/SpecSeal

Skill Claude CodeCodex

Spec-driven implementation methodology: document layout (specs/ + .specseal/), policy-first judgment, evidence feedback, and review incorporation. Use when: implementing a feature, starting a ticket — including deciding how to start one, incorporating review feedback, or when a repo needs its document layout…

MichaelYcJo/SpecSeal

Skill Claude CodeCodex

Record an insight that cost real debugging effort and cannot be recovered from a search — project-specific causes, dependency quirks, the reason behind an architectural choice. Use when: something was just figured out the hard way and the next session would otherwise pay for it again. NOT for: narrating ordinary work…

MichaelYcJo/SpecSeal

Skill Claude CodeCodex

Behavior-equivalence methodology for legacy migrations: three-way judgment (policy ↔ original code ↔ new code) with original-preservation as the default. Use when: a project declares a migration config (.specseal/parity.md), porting or reviewing ported behavior, judging divergence from a legacy original. NOT for…

MichaelYcJo/SpecSeal

Skill Claude CodeCodex

Declare that this repo ports behavior from another codebase — find the original, record the baseline, write .specseal/parity.md.

MichaelYcJo/SpecSeal

Skill Claude CodeCodex

Merge the specseal CLAUDE.md block into the user's CLAUDE.md with semantic dedup — propose, get approval, then apply.