traceweaver-core

Plugin traceweaver-core from marketplace traceweaver in Oxiom-Systems/traceweaver. Commands read from the repo's manifest — 19 days ago.

Skills (55)

• baseline-configuration-control

  Controls baseline identity, configuration control, fork-diff classification, and evidence currency for TraceWeaver work. Use when deciding which approved baseline governs the work, whether evidence still applies after later changes, whether a changed file resets a gate, or before release, promotion,

• ce-brainstorm

  Explore vague or ambitious ideas into a right-sized requirements-only unified plan. Use when the user wants to brainstorm, think through scope, decide what to build, or needs collaborative product framing before planning. Also use when the user must scope work in territory they say they do not know

• ce-code-review

  Structured code review for bugs, regressions, tests, and standards. Use before PRs or when asked for review; report-only by default, with explicit local apply available for user-directed fix workflows.

• ce-commit-push-pr

  Internal TraceWeaver publication engine. Draft freely, but mutate Git or GitHub only with a current single-use authorization capsule issued by tw-commit-push-pr for the exact repository, tree, target, operations, and credential identity.

• ce-commit

  Draft a clear, value-communicating commit message without staging or committing in the TraceWeaver packaged alpha. Use when the user asks to commit or save changes, then report that commit remains held by TraceWeaver publication gates.

• ce-compound-refresh

  Refresh docs/solutions learnings against the current codebase. Use when auditing stale, overlapping, superseded, or drifted learnings; avoid general refactor, debugging, or code review unless docs/solutions is explicit.

• ce-compound

  Document a recently solved problem or durable project vocabulary in docs/solutions/ or CONCEPTS.md. Use when capturing a learning after work.

• ce-debug

  Diagnosis loop for bugs and failing behavior. Use for errors, stack traces, regressions, failed tests, issue-tracker bugs, stuck investigations after failed fixes, or asks to debug/fix a bug.

• ce-doc-review

  Review requirements, plans, or specs with role-specific lenses. Use when the user wants to improve an existing planning document.

• ce-ideate

  Generate and evaluate grounded ideas. Use when the user asks for ideas, improvements, surprising options, or AI-generated directions before choosing one to develop; use ce-brainstorm to refine the user's own idea.

• ce-plan

  Create structured plans for multi-step work, including software and non-software tasks. Use when asked to plan, break down implementation, plan from requirements, or deepen an existing plan; prefer ce-brainstorm for exploratory framing.

• ce-resolve-pr-feedback

  Resolve PR review feedback. Use when addressing review comments, resolving review threads, or fixing code-review feedback.

• ce-sessions

  Search and ask questions about coding agent session history across Claude Code, Codex, and Cursor. Use when asking what was worked on, what was tried before, how a problem was investigated across sessions, what happened recently, or any question about past agent sessions. Also use when the user refe

• ce-setup

  Check Compound Engineering health and repo-local config.

• ce-strategy

  Create or update STRATEGY.md. Use when starting a product, changing direction or roadmap, or when ce-ideate, ce-brainstorm, or ce-plan need upstream product grounding.

• ce-test-browser

  Run browser tests for pages affected by the current branch or PR.

• ce-test-xcode

  Build and test iOS apps on simulator with XcodeBuildMCP.

• ce-work

  Execute a plan or concrete work prompt end-to-end. Use when implementing from docs/plans, a spec path, or a clear build request; use ce-debug for open-ended bugs. Standalone use owns the shipping tail; outer orchestrators pass `mode:return-to-caller [implementation_engine:<compact-json>] [implementa

• ce-worktree

  Set up isolated git worktrees — create a new branch for fresh work, or attach a worktree to an existing branch/PR/commit to work on it in isolation. Use when starting isolated work or isolating an existing ref; detects existing isolation first.

• lfg

  TraceWeaver-controlled compatibility alias for full autonomous engineering workflow. Delegates to tw-auto so CE-style automation runs under Intent Contract, authority, traceability, verification, and stop-before-commit controls.

• requirements-reviewer

  Reviews requirement quality and approval readiness for planning, specs, PRDs, traceability matrices, acceptance criteria, and document reviews. Use when deciding whether a need, requirement, user story, constraint, or acceptance criterion is good enough to become approved implementation authority, o

• risk-gap-change-control

  Controls approved gaps, accepted risks, weak-requirement exceptions, traceability debt, deferred verification or validation, and requirement changes so known weaknesses stay visible, owned, bounded, and reviewable. Use when work cannot meet the normal authority, traceability, V&V, or baseline path,

• systems-engineering-traceability

  Maintains traceability for agent-generated behavior from idea and stakeholder need through requirement, design, implementation, verification, and validation. Use when refining ideas that may become work, starting or changing meaningful behavior, reviewing unclear code, auditing agent output, plannin

• technical-review-and-audit-gate

  Judges whether work is ready to pass a lifecycle gate by checking entry criteria, exit criteria, evidence completeness, review-lens coverage, action-item disposition, and risk state, then issuing a proceed, hold, reduce, or reject decision. Use when deciding whether work may pass an implementation,

• tw-audit

  TraceWeaver-controlled audit wrapper for checking a project's requirements authority, code traces, verification evidence, and validation or acceptance closure before cleanup, completion, or release claims.

• tw-authority-gate

  TraceWeaver adapter for checking whether planned implementation work has approved authority before build work starts. Use before ce-work, implementation, or task execution on meaningful behavior.

• tw-auto

  TraceWeaver consolidated delivery controller. Use for approved work that should remain in one Sol main context through planning, implementation, verification, trace updates, integrated review, and at most one batched repair.

• tw-brainstorm

  TraceWeaver-controlled brainstorm wrapper. Use when exploring vague ideas, requirements source material, or possible approaches while preserving source-evidence status before requirements review.

• tw-code-review

  TraceWeaver integrated candidate review. Use for one independent review of a frozen behavior or mixed candidate, covering code, tests, relevant normative docs, traceability, correctness, and triggered risk lenses in one reviewer context.

• tw-commit-push-pr

  TraceWeaver-controlled commit, push, and PR wrapper. Use when the user asks to commit and PR, push, ship, open a pull request, update a PR description, or prepare publication while preserving TraceWeaver publication-route controls.

• tw-commit

  TraceWeaver-controlled commit wrapper. Use when the user asks to commit, save changes, or prepare a commit while preserving Intent Contract, traceability, verification, review, and publication-route controls.

• tw-compound-refresh

  TraceWeaver-controlled stale-learning refresh wrapper. Use when refreshing docs/solutions learning material while keeping authority and requirements mutation held.

• tw-compound

  TraceWeaver-controlled learning-capture wrapper. Use when documenting a solved problem as source evidence without rewriting requirements or publication state.

• tw-debug

  TraceWeaver-controlled debugging wrapper. Use when debugging errors, failing tests, regressions, production issues, or broken behavior while preserving TraceWeaver authority, traceability, verification, and no-publication controls.

• tw-doc-review

  Standalone TraceWeaver authority/document review. Use only for authority-only or document-only semantic changes; mixed implementation candidates are reviewed once through tw-code-review.

• tw-graph

  TraceWeaver-owned deterministic authority projection and freshness control surface. Use for source-located requirement/trace navigation, impact and duplicate candidates, accepted-cycle refresh, and required review/PR freshness checks.

• tw-grill

  Optional TraceWeaver intent-deepening interview after ideation and before brainstorming. Use when a selected idea, plan, or design needs relentless questioning before requirements are drafted.

• tw-ideate
• tw-lifecycle
• tw-plan
• tw-requirements-review
• tw-resolve-pr-feedback
• tw-sessions
• tw-setup
• tw-strategy
• tw-test-browser
• tw-test-xcode
• tw-traceability-check
• tw-update
• tw-vv-define
• tw-work
• tw-worktree
• using-agent-skills
• validation-planner
• verification-planner

Subagents (43)

• ce-adversarial-document-reviewer

  Conditional document-review persona for high-stakes documents -- those with significant architectural decisions, new abstractions, or more than 5 requirements. Challenges premises, surfaces unstated assumptions, and stress-tests decisions rather than evaluating document quality.

• ce-adversarial-reviewer

  Conditional code-review persona, selected when the diff is large (>=50 changed lines) or touches high-risk domains like auth, payments, data mutations, or external APIs. Actively constructs failure scenarios to break the implementation rather than checking against known patterns.

• ce-agent-native-reviewer

  Reviews code to ensure agent-native parity -- any action a user can take, an agent can also take. Use after adding UI features, agent tools, or system prompts.

• ce-ankane-readme-writer

  Creates or updates README files following Ankane-style template for Ruby gems. Use when writing gem documentation with imperative voice, concise prose, and standard section ordering.

• ce-api-contract-reviewer

  Conditional code-review persona, selected when the diff touches API routes, request/response types, serialization, versioning, or exported type signatures. Reviews code for breaking contract changes.

• ce-architecture-strategist

  Analyzes code changes from an architectural perspective for pattern compliance and design integrity. Use when reviewing PRs, adding services, or evaluating structural refactors.

• ce-best-practices-researcher

  Researches and synthesizes external best practices, documentation, and examples for any technology or framework. Use when you need industry standards, community conventions, or implementation guidance.

• ce-code-simplicity-reviewer

  Final review pass to ensure code is as simple and minimal as possible. Use after implementation is complete to identify YAGNI violations and simplification opportunities.

• ce-coherence-reviewer

  Reviews planning documents for internal consistency -- contradictions between sections, terminology drift, structural issues, and ambiguity where readers would diverge. Spawned by the document-review skill.

• ce-correctness-reviewer

  Always-on code-review persona. Reviews code for logic errors, edge cases, state management bugs, error propagation failures, and intent-vs-implementation mismatches.

• ce-data-integrity-guardian

  Reviews database migrations, data models, and persistent data code for safety. Use when checking migration safety, data constraints, transaction boundaries, or privacy compliance.

• ce-data-migration-reviewer

  Conditional code-review persona for migration files, schema dumps, backfills, and data transformations. Covers schema drift, mapping correctness, deploy-window safety, and verification plans.

• ce-deployment-verification-agent

  Produces Go/No-Go deployment checklists with SQL verification queries, rollback procedures, and monitoring plans. Use when PRs touch production data, migrations, or risky data changes.

• ce-design-implementation-reviewer

  Visually compares live UI implementation against Figma designs and provides detailed feedback on discrepancies. Use after writing or modifying HTML/CSS/React components to verify design fidelity.

• ce-design-iterator

  Iteratively refines UI design through N screenshot-analyze-improve cycles. Use PROACTIVELY when design changes aren't coming together after 1-2 attempts, or when user requests iterative refinement.

• ce-design-lens-reviewer

  Reviews planning documents for missing design decisions -- information architecture, interaction states, user flows, and AI slop risk. Uses dimensional rating to identify gaps. Spawned by the document-review skill.

• ce-feasibility-reviewer

  Evaluates whether proposed technical approaches in planning documents will survive contact with reality -- architecture conflicts, dependency gaps, migration risks, and implementability. Spawned by the document-review skill.

• ce-figma-design-sync

  Detects and fixes visual differences between a web implementation and its Figma design. Use iteratively when syncing implementation to match Figma specs.

• ce-framework-docs-researcher

  Gathers comprehensive documentation and best practices for frameworks, libraries, or dependencies. Use when you need official docs, version-specific constraints, or implementation patterns.

• ce-git-history-analyzer

  Performs archaeological analysis of git history to trace code evolution, identify contributors, and understand why code patterns exist. Use when you need historical context for code changes.

• ce-issue-intelligence-analyst

  Fetches and analyzes GitHub issues to surface recurring themes, pain patterns, and severity trends. Use when understanding a project's issue landscape, analyzing bug patterns for ideation, or summarizing what users are reporting.

• ce-julik-frontend-races-reviewer

  Conditional code-review persona, selected when the diff touches async UI code, Stimulus/Turbo lifecycles, or DOM-timing-sensitive frontend behavior. Reviews code for race conditions and janky UI failure modes.

• ce-learnings-researcher

  Searches docs/solutions/ for applicable past learnings via frontmatter metadata (bugs, architecture, design patterns, conventions, workflow learnings). Use before implementing features, making decisions, or starting work in a documented area so institutional knowledge carries forward.

• ce-maintainability-reviewer

  Always-on code-review persona. Reviews code for structural quality, complexity deletion, coupling, naming, dead code, type-boundary leaks, and abstraction debt.

• ce-pattern-recognition-specialist

  Analyzes code for design patterns, anti-patterns, naming conventions, and duplication. Use when checking codebase consistency or verifying new code follows established patterns.

• ce-performance-oracle

  Analyzes code for performance bottlenecks, algorithmic complexity, database queries, memory usage, and scalability. Use after implementing features or when performance concerns arise.

• ce-performance-reviewer

  Conditional code-review persona, selected when the diff touches database queries, loop-heavy data transforms, caching layers, or I/O-intensive paths. Reviews code for runtime performance and scalability issues.

• ce-pr-comment-resolver

  Evaluates and resolves one or more related PR review threads -- assesses validity, implements fixes, and returns structured summaries with reply text. Spawned by the resolve-pr-feedback skill.

• ce-previous-comments-reviewer

  Conditional code-review persona, selected when reviewing a PR that has existing review comments or review threads. Checks whether prior feedback has been addressed in the current diff.

• ce-product-lens-reviewer

  Reviews planning documents as a senior product leader -- challenges premise claims, assesses strategic consequences (trajectory, identity, adoption, opportunity cost), and surfaces goal-work misalignment. Spawned by the document-review skill.

• ce-project-standards-reviewer

  Always-on code-review persona. Audits changes against the project's own CLAUDE.md and AGENTS.md standards -- frontmatter rules, reference inclusion, naming conventions, cross-platform portability, and tool selection policies.

• ce-reliability-reviewer

  Conditional code-review persona, selected when the diff touches error handling, retries, circuit breakers, timeouts, health checks, background jobs, or async handlers. Reviews code for production reliability and failure modes.

• ce-repo-research-analyst

  Conducts thorough research on repository structure, documentation, conventions, and implementation patterns. Use when onboarding to a new codebase or understanding project conventions.

• ce-scope-guardian-reviewer

  Reviews planning documents for scope alignment and unjustified complexity -- challenges unnecessary abstractions, premature frameworks, and scope that exceeds stated goals. Spawned by the document-review skill.

• ce-security-lens-reviewer

  Evaluates planning documents for security gaps at the plan level -- auth/authz assumptions, data exposure risks, API surface vulnerabilities, and missing threat model elements. Spawned by the document-review skill.

• ce-security-reviewer

  Conditional code-review persona, selected when the diff touches auth middleware, public endpoints, user input handling, or permission checks. Reviews code for exploitable vulnerabilities.

• ce-security-sentinel

  Performs security audits for vulnerabilities, input validation, auth/authz, hardcoded secrets, and OWASP compliance. Use when reviewing code for security issues or before deployment.

• ce-session-historian

  Synthesizes findings from prior coding-agent sessions about the same problem or topic. Receives pre-extracted skeleton/error file paths from a `ce-sessions` orchestrator and returns prose findings — investigation journey, what didn't work, key decisions, related context. Not intended for direct disp

• ce-slack-researcher

  Searches Slack for organizational context -- decisions, constraints, and discussions that may not be documented elsewhere. Use when the user explicitly asks to search Slack for context during ideation, planning, or brainstorming.

• ce-spec-flow-analyzer

  Analyzes specifications and feature descriptions for user flow completeness and gap identification. Use when a spec, plan, or feature description needs flow analysis, edge case discovery, or requirements validation.

• ce-swift-ios-reviewer

  Conditional code-review persona, selected when the diff touches Swift files, SwiftUI/UIKit views, iOS entitlements, privacy manifests, Core Data models, SPM manifests, storyboards/XIBs, or semantic .pbxproj changes. Reviews for SwiftUI correctness, state management, memory safety, Swift concurrency,

• ce-testing-reviewer

  Always-on code-review persona. Reviews code for test coverage gaps, weak assertions, brittle implementation-coupled tests, and missing edge case coverage.

• ce-web-researcher

  Performs iterative web research and returns structured external grounding. Use when ideating outside the codebase, validating prior art, scanning competitor patterns, finding cross-domain analogies, or fetching market signals. Prefer over manual web searches for structured external context.

Hooks (1)

• SessionStart

  "${CLAUDE_PLUGIN_ROOT}/hooks/run-hook.cmd" session-start

Similar plugins