NeoLabHQ/context-engineering-kit - Page 2

plan-do-check-act

Iterative PDCA cycle for systematic experimentation and continuous improvement

plan-task

Refine a draft task specification into a fully planned, implementation-ready task with acceptance criteria, architecture, per-step sub-task files and verifiable phases

prompt-engineering

Use this skill when you writing commands, hooks, skills for Agent, or prompts for sub agents or any other LLM interaction, including optimizing prompts, improving LLM outputs, or designing production prompt templates.

propose-hypotheses

Execute complete FPF cycle from hypothesis generation to decision

query

Search the FPF knowledge base and display hypothesis details with assurance information

reflect

Reflect on previus response and output, based on Self-refinement framework for iterative improvement with complexity triage and verification

reset

Reset the FPF reasoning cycle to start fresh

resolve-fixed-pr-comments

Verify what PR review comments have been addressed (committed/pushed OR uncommitted local changes) and resolve the threads that are genuinely fixed or no longer relevant.

review-local-changes

Review your local uncommitted working-tree changes (git diff plus untracked files) and return actionable improvement suggestions. Use before committing, when nothing has been pushed yet.

review-pr

Review an existing GitHub pull request and post inline review comments on its diff. Use when the changes are on an opened PR rather than your local working tree.

root-cause-tracing

Use when errors occur deep in execution and you need to trace back to find the original trigger - systematically traces bugs backward through call stack, adding instrumentation when needed, to identify source of invalid data or incorrect behavior

setup-arxiv-mcp

Guide for setup arXiv paper search MCP server using Docker MCP

setup-codemap-cli

Guide for setup Codemap CLI for intelligent codebase visualization and navigation

setup-context7-mcp

Guide for setup Context7 MCP server to load documentation for specific technologies.

setup-serena-mcp

Guide for setup Serena MCP server for semantic code retrieval and editing capabilities

status

Display the current state of the FPF knowledge base

subagent-driven-development

Use when executing implementation plans with independent tasks in the current session or facing 3+ independent issues that can be investigated without shared state or dependencies - dispatches fresh subagent for each task with code review between tasks,…

test-coverage

Use after writing tests to assess coverage quality across structural, mutation, requirements, and API/integration dimensions; organized knowledge for choosing and interpreting coverage analyses.

test-driven-development

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

test-prompt

Use when creating or editing any prompt (commands, hooks, skills, subagent instructions) to verify it produces desired behavior - applies RED-GREEN-REFACTOR cycle to prompt engineering using subagents for isolated testing

test-skill

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…

thought-based-reasoning

Use when tackling complex reasoning tasks requiring step-by-step logic, multi-step arithmetic, commonsense reasoning, symbolic manipulation, or problems where simple prompting fails - provides comprehensive guide to Chain-of-Thought and related prompting…

traiage-review

This skill should be used when need prioritize what changed code in repository human must review.

tree-of-thoughts

Execute tasks through systematic exploration, pruning, and expansion using Tree of Thoughts methodology with meta-judge evaluation specifications and multi-agent evaluation

update-docs

Update and maintain project documentation for local code changes using multi-agent workflow with tech-writer agents. Covers docs/, READMEs, JSDoc, and API documentation.

why

Iterative Five Whys root cause analysis drilling from symptoms to fundamentals

write-concisely

Apply writing rules to any documentation that humans will read. Makes your writing clearer, stronger, and more professional.

write-tests

Add missing test coverage for your local code changes by generating new test files (covers uncommitted and untracked changes, or the latest commit if everything is committed). Use when you want write tests for new logic or increase test coverage.

create-command

Interactive assistant for creating new Claude commands with proper structure, patterns, and MCP tool integration

plan-task

Refine a draft task specification into a fully planned, implementation-ready task with acceptance criteria, architecture, per-step sub-task files and verifiable phases

implement-task

Implement a task step by step with automated LLM-as-Judge verification at the end of each phase

do-and-judge

Execute a task with sub-agent implementation and LLM-as-a-judge verification with automatic retry loop

do-in-steps

Execute one complex task as ordered, dependent steps run sequentially, passing context from each step to the next, with per-step LLM-as-a-judge verification. Use when later steps depend on the results of earlier ones.

launch-sub-agent

Launch an intelligent sub-agent with automatic model selection based on task complexity, specialized agent matching, Zero-shot CoT reasoning, and mandatory self-critique verification

add-task

creates draft task file in .specs/tasks/draft/ with original user intent

do-in-parallel

Run independent tasks concurrently across multiple files or targets using parallel sub-agents, with per-task model selection and LLM-as-a-judge verification. Use when tasks do not depend on each other and can run side by side.

review-local-changes

Review your local uncommitted working-tree changes (git diff plus untracked files) and return actionable improvement suggestions. Use before committing, when nothing has been pushed yet.

review-pr

Review an existing GitHub pull request and post inline review comments on its diff. Use when the changes are on an opened PR rather than your local working tree.

write-tests

Add missing test coverage for your local code changes by generating new test files (covers uncommitted and untracked changes, or the latest commit if everything is committed). Use when you want write tests for new logic or increase test coverage.

load-pr-comments

Use to load open/unresolved PR review comments then aggregate them as tasks in .specs/comments/*.md for parallel agents to fix.