core-engineering

Plugin core-engineering from marketplace moonsong-labs in Moonsong-Labs/knowledge-work-plugins. Commands read from the repo's manifest — 1 month ago.

Skills (13)

• brainstorming

  You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

• dispatching-parallel-agents

  Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies

• executing-plans

  Use when you have a written implementation plan to execute in a separate session with review checkpoints

• finishing-a-development-branch

  Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup

• receiving-code-review

  Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation

• requesting-code-review

  Use when completing tasks, implementing major features, or before merging to verify work meets requirements

• subagent-driven-development

  Use when executing implementation plans with independent tasks in the current session

• systematic-debugging

  Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes

• test-driven-development

  Use when implementing any feature or bugfix, before writing implementation code

• using-git-worktrees

  Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback

• using-skills

  Use when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions

• verification-before-completion

  Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always

• writing-plans

  Use when you have a spec or requirements for a multi-step task, before touching code

Subagents (4)

• dependency-manager

  Use proactively when working with dependencies — package.json, Cargo.toml, go.mod, pyproject.toml, requirements.txt, pom.xml, build.gradle. Triggers: vulnerability scanning, CVE remediation, version conflict resolution, dependency audit, bundle size optimization, lock file issues, breaking upgrades,

• documentation-specialist

  Use when creating or improving documentation — API docs, tutorials, architecture guides, README files, getting-started guides, migration guides. Triggers: API documentation with code examples, tutorial creation, documentation audit for staleness or gaps, architecture decision records, changelog writ

• git-workflow-manager

  Use when designing or improving Git workflows — branching strategies, merge policies, release automation, repository maintenance. Triggers: branching strategy design, merge conflict reduction, release process automation, semantic versioning setup, changelog generation, commit convention enforcement,

• rust-specialist

  Use proactively when working on Rust code — .rs files, Cargo.toml, cargo commands. Triggers: borrow checker errors, lifetime annotations, ownership/borrowing design, trait system design (object safety, async traits, HRTBs), async patterns (tokio, select!, cancellation safety), unsafe code review, pe

Hooks (1)

• SessionStart

  "${CLAUDE_PLUGIN_ROOT}/hooks/session-start"

Similar plugins