Topic: developer-tools
13,276 skills in this topic.
-
quick-start
Interactive onboarding for the MCP Task Orchestrator. Detects empty or populated workspaces and walks through how plan mode, persistent tracking, and the MCP work together. Use when a user says "get started", "how do I use this", "quick start", "first time setup", "onboard me", "what can this MCP do", or "help me learn task orchestrator".
jpicklyk/task-orchestrator 177
-
validate
Run the full quality gate — tests, lint, build, and cortex-tms validate --strict.
cortex-tms/cortex-tms 173
-
release
Guide through the Cortex TMS release process — version bump, changelog, sync, tag, publish. Every step requires user approval.
cortex-tms/cortex-tms 173
-
new-command
Scaffold a new CLI command for Cortex TMS following the existing codebase patterns.
cortex-tms/cortex-tms 173
-
plan
Research the codebase and create an implementation plan following Propose/Justify/Recommend. Use this before any feature, fix, or refactor.
cortex-tms/cortex-tms 173
-
implement
Implement an approved plan. Write code, tests, and docs following the sprint checklist in NEXT-TASKS.md.
cortex-tms/cortex-tms 173
-
sync
Synchronize task files and source-of-truth documents. Update NEXT-TASKS.md, FUTURE-ENHANCEMENTS.md, README, and CHANGELOG to reflect current project state.
cortex-tms/cortex-tms 173
-
observatory
Self-improving flywheel that analyzes agent traces, surfaces improvement signals, and proposes targeted system enhancements.
juanandresgs/claude-ctrl 173
-
decide
Generate an interactive decision configurator from research or plan analysis. Presents options as explorable cards with trade-offs, costs, and filtering. Integrates with Planner to collect DEC-ID decisions.
juanandresgs/claude-ctrl 173
-
prd
Write structured feature specifications with problem statements, user journeys, use cases, functional requirements, and success metrics. Use when describing a problem space, developing a PRD, defining acceptance criteria, prioritizing requirements, or documenting product decisions.
juanandresgs/claude-ctrl 173
-
consume-content
Produce a faithful content-snapshot of any source material (article, report, PDF, advisory) with verbatim quotes, structural transparency, and labeled editorial.
juanandresgs/claude-ctrl 173
-
context-preservation
Generate structured context summaries for session continuity across compaction
juanandresgs/claude-ctrl 173
-
rewind
List and restore to a named checkpoint from the current session. Use when the agent has gone off track and you need to recover to a previous good state.
juanandresgs/claude-ctrl 173
-
diagnose
Validate hook integrity, state file consistency, and system health for the ~/.claude configuration.
juanandresgs/claude-ctrl 173
-
deep-research
Multi-model deep research with comparative assessment (OpenAI + Perplexity + Gemini). Queries 3 deep research providers in parallel and produces a comparative synthesis.
juanandresgs/claude-ctrl 173
-
reckoning
Analyze a project's MASTER_PLAN.md to assess coherence, evolution trajectory, and intent alignment. Modes: default (full analysis), compare (delta between reckonings), operationalize (convert findings to actionable work via /decide), steer (strategic brainstorming grounded in findings).
juanandresgs/claude-ctrl 173
-
think
Use before planning when you need strategic clarity — product discovery, scope decisions, premise validation. Applies YC-grade product thinking to challenge assumptions and find the narrowest valuable wedge. Supports --autopilot to run the full sprint automatically after approval. Triggers on /think, /office-hours, /ceo-review.
garagon/nanostack 173
-
guard
Use when working near production, sensitive systems, or destructive operations. Activates on-demand safety hooks that block dangerous commands. Supports modes — careful (warn), freeze (block writes outside scope), unfreeze (remove restrictions). Triggers on /guard, /careful, /freeze, /unfreeze.
garagon/nanostack 173
-
qa
Use to verify that code works correctly — browser-based testing with Playwright, native app testing with computer use, CLI testing, API testing, or root-cause debugging. Supports --quick, --standard, --thorough modes. Triggers on /qa.
garagon/nanostack 173
-
review
Use after writing code to get a thorough code review. Runs two passes — structural correctness then adversarial edge-case hunting. Scales depth by diff size. Supports --quick, --standard, --thorough modes. Triggers on /review.
garagon/nanostack 173
-
nano-run
First-time setup and guided sprint. Configures stack, permissions, and work preferences conversationally. Run once after installing nanostack. Triggers on /nano-run.
garagon/nanostack 173
-
nano-help
Quick reference for all nanostack commands. Shows available skills, what each one does, and how to use them. Triggers on /nano-help.
garagon/nanostack 173
-
feature
Add a feature to an existing project with a full sprint. Skips /think diagnostic, goes straight to planning. Use when the user knows what they want and the project already exists. Triggers on /feature.
garagon/nanostack 173
-
compound
Document what you learned during this sprint. Reads artifacts, writes structured solutions to know-how/solutions/. Run after /ship or after fixing a significant bug. Triggers on /compound.
garagon/nanostack 173