movebrickschi/harness-engineering-mcp
Skill Claude CodeCodex
A step-by-step workflow for changing code structure without changing what the software does. It requires tests around the code, small commits, and passing tests after each change.
movebrickschi/harness-engineering-mcp
Skill Claude CodeCodex
A step-by-step workflow for changing code structure without changing what the software does. It requires tests around the code, small commits, and passing tests after each change.
movebrickschi/harness-engineering-mcp
Skill Claude CodeCodex
Use when completing tasks, implementing major features, or before merging to verify work meets requirements - dispatches superpowers:code-reviewer subagent to review implementation against plan or requirements before proceeding.
movebrickschi/harness-engineering-mcp
Skill Claude CodeCodex
Use when you've developed a broadly useful skill and want to contribute it upstream via pull request - guides process of branching, committing, pushing, and creating PR to contribute skills back to upstream repository.
movebrickschi/harness-engineering-mcp
Skill Claude CodeCodex
Use when executing implementation plans with independent tasks in the current session - dispatches fresh subagent for each task with code review between tasks, enabling fast iteration with quality gates.
movebrickschi/harness-engineering-mcp
Skill Claude CodeCodex
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes - four-phase framework (root cause investigation, pattern analysis, hypothesis testing, implementation) that ensures understanding before attempting solutions.
movebrickschi/harness-engineering-mcp
Skill Claude CodeCodex
Use when implementing any feature or bugfix, before writing implementation code - write the test first, watch it fail, write minimal code to pass; ensures tests actually verify behavior by requiring failure first.
movebrickschi/harness-engineering-mcp
Skill Claude CodeCodex
Use when writing or changing tests, adding mocks, or tempted to add test-only methods to production code - prevents testing mock behavior, production pollution with test-only methods, and mocking without understanding dependencies.
movebrickschi/harness-engineering-mcp
Skill Claude CodeCodex
Use when creating or editing skills, before deployment, to verify they work under pressure and resist rationalization - applies RED-GREEN-REFACTOR cycle to process documentation by running baseline without skill, writing to address failures, iterating to close loopholes.
movebrickschi/harness-engineering-mcp
Skill Claude CodeCodex
A workflow for connecting an application to an outside service such as payments, messaging, login, text messages, file storage, maps, or an AI provider.
movebrickschi/harness-engineering-mcp
Skill Claude CodeCodex
Use when starting any conversation - establishes mandatory workflows for finding and using skills, including using Skill tool before announcing usage, following brainstorming before coding, and creating TodoWrite todos for checklists.
movebrickschi/harness-engineering-mcp
Skill Claude CodeCodex
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.
movebrickschi/harness-engineering-mcp
Skill Claude CodeCodex
A workflow for writing Chinese-language technology articles for WeChat, a messaging and publishing platform widely used in China, from recent news or a chosen topic.
movebrickschi/harness-engineering-mcp
Skill Claude CodeCodex
Use when design is complete and you need detailed implementation tasks for engineers with zero codebase context - creates comprehensive implementation plans with exact file paths, complete code examples, and verification steps assuming engineer has minimal domain knowledge.
movebrickschi/harness-engineering-mcp
Skill Codex
Use when creating new skills, editing existing skills, or verifying skills work before deployment - applies TDD to process documentation by testing with subagents before writing, iterating until bulletproof against rationalization.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: