stepwise-core

Plugin stepwise-core from marketplace stepwise-dev in nikeyes/stepwise-dev. Commands read from the repo's manifest — 9 days ago.

Skills (14)

• bugmagnet

  Lightweight bug discovery and test coverage analysis for a code module. Use when the user asks to find bugs, analyze test coverage, write edge case tests, or do exploratory testing on a file. Triggers on "bugmagnet", "find bugs in", "test coverage gaps", "edge cases for", or "exploratory testing on

• create-plan

  Create detailed implementation plans through interactive research and iteration

• grill-me

  Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".

• hamburger-method

  Slices features into vertical deliverable pieces using the Hamburger Method. Generates 4-5 implementation options per layer and composes minimal end-to-end slices. Use when slicing work, breaking down features into layers, or delivering incrementally.

• implement-plan

  Implement technical plans from thoughts/shared/plans with verification

• iterate-plan

  Update an existing implementation plan in thoughts/shared/plans/ from feedback, checking the change against the code. Use when the user asks to change, extend or cut a plan.

• mutation-testing

  Finds weak or missing tests by checking whether small code changes (mutants) would be caught by the test suite, then hands the gaps to TDD. Use when verifying test effectiveness, asking "would my tests catch this bug?", hunting surviving mutants, or checking changed code after TDD. Triggers on "muta

• research-codebase

  Document codebase as-is with thoughts directory for historical context

• small-safe-steps

  Small Safe Steps (S3): breaks work into 1-3h increments with zero downtime. Use when asking "how do I implement/migrate/refactor", "what steps to do X", "plan safe migration", or handling risky DB/API changes. Applies expand-contract pattern for migrations, refactorings, schema changes.

• story-splitting

  Detects stories that are too big and applies splitting heuristics. Identifies linguistic red flags (and, or, manage, handle, including) and suggests concrete splitting strategies. Use when breaking down requirements or splitting large work.

• tdd

  Test-driven development with red-green-refactor loop. Use when user wants to build features or fix bugs using TDD, mentions "red-green-refactor", wants integration tests, or asks for test-first development.

• test-desiderata

  Analyze and improve test code quality using Kent Beck's Test Desiderata framework. Use when analyzing test files, reviewing test code, identifying test quality issues, suggesting test improvements, or when asked to evaluate tests against best practices. Applies to unit tests, integration tests, and

• thoughts-management

  Manage thoughts directory operations including initialization and metadata generation. Use when initializing a new project's thoughts/ structure or when gathering git metadata for document frontmatter.

• validate-plan

  Validate that plan was correctly implemented, verify all success criteria

Subagents (5)

• codebase-analyzer

  Analyzes codebase implementation details. Call the codebase-analyzer agent when you need to find detailed information about specific components. As always, the more detailed your request prompt, the better! :)

• codebase-locator

  Locates files, directories, and components relevant to a feature or task. Call `codebase-locator` with human language prompt describing what you're looking for. Basically a "Super Grep/Glob/LS tool" — Use it if you find yourself desiring to use one of these tools more than once.

• codebase-pattern-finder

  codebase-pattern-finder is a useful subagent_type for finding similar implementations, usage examples, or existing patterns that can be modeled after. It will give you concrete code examples based on what you're looking for! It's sorta like codebase-locator, but it will not only tell you the locatio

• thoughts-analyzer

  The research equivalent of codebase-analyzer. Use this subagent_type when wanting to deep dive on a research topic. Not commonly needed otherwise.

• thoughts-locator

  Discovers relevant documents in the thoughts/ directory. Use when you need to find research, plans, notes, or tickets related to a topic.

Similar plugins