new
193Command
A command that registers a new project in a shared memory file, assigning it the next free number and optionally recording its description and folder.
962 tagged agentic-coding, measured the same way as everything else here.
Browse within: ai-coding 419ai-development 186anthropic-skills 115agentic-workflow 95agent-orchestration 76ai-assistant 69ai-pair-programming 69ai-security 69best-practices 66ai-workflow 54auto-learning 44claude-code-skills 44claude-code-subagents 44coding-agents 43
Command
A command that registers a new project in a shared memory file, assigning it the next free number and optionally recording its description and folder.
Master0fFate/parallax-claudecode
Command
Part of parallax-claudecode
Summarize the current session and run package/native lifecycle diagnostics.
Command
Part of vibeframe
Plan and implement a feature through the VibeFrame model (context → declare → implement → link → validate).
Command
Part of vibeframe
Explain unmapped code changes and fold them into the VibeFrame model.
Command
Part of vibeframe
Walk the VibeFrame drift inbox and resolve each finding (fix / accept / dismiss).
Command
HR-AI / AEDT bias audit. Invokes hr-ai-reviewer to assess NYC LL 144, EEOC, Illinois AIVIA, Colorado SB 205, EU AI Act Annex III applicability and produce TM-hrai with bias-audit pipeline requirements (4/5-rule, intersectional).
Command
Gracefully retire an LLM agent from the workforce. Archives prompt, removes from sync list, keeps verdicts for audit. Like firing a human — but reversible.
Command
Performance review for an LLM agent (or all agents). Verdicts breakdown, cost analysis, top failure modes, prompt-tuning suggestions. Like a human '1:1' but for AI workforce.
Command Claude Code
Use the "consult7" MCP server to request help from "openai/gpt-5", or the model explicitly specified, regarding the following request. Send it the following request, along with the relevant codebase, ALWAYS EXCLUDING all files and folders described in .claudeignore and .gitignore, as well as any file for which the…
Command Claude Code
For this task only, act as a Claude sub-agent expert providing recommendations for what new Claude sub-agents are relevant to add to the project, or to satisfy the user's intent should they have provided one. You understand that sub-agents have their own context and are not aware of what other sub-agents are doing, or…
Command
Use when an agent should inspect the current Harness Forge workspace state before acting.
Command
Use when an agent should inspect Harness Forge task-runtime folders, task packs, and linked artifacts for the current work item.
Command
Use when an agent should preview or apply a non-destructive Harness Forge package refresh while preserving gathered runtime state.
Command
Use when a task needs structure, sequencing, risks, and validation checkpoints.
Command
Use when defining or running verification for code, docs, templates, or migration work.
Command
Read-only cross-check of spec, plan, and tasks for consistency, duplication, gaps, and constitution violations before implementation starts.
Command
Systematically find and resolve the highest-impact ambiguities in a spec before planning starts, instead of discovering them mid-implementation.
Command
Create or update the project's constitution — the small set of non-negotiable product/architecture principles every spec, plan, and implementation must be checked against.
Command
Execute a task list in dependency order, tests before implementation for each task, halting on any non-parallel failure instead of pressing ahead.
Command
Turn a clarified spec into a concrete technical plan — architecture, data model, and interfaces — before any task breakdown or code.
Command
Turn a short feature request into a written spec — user-facing behavior and testable acceptance criteria, deliberately free of implementation detail — before any planning starts.
Command
Turn a plan into an ordered, independently-checkable task list, with every task traceable back to a requirement and every requirement covered by at least one task.
Command
Pre-deployment evaluation checklist — holdout eval, baseline comparison, leakage scan, failure mode documentation.
Command
Scaffold a new tracked experiment — create notebook, set up tracking, log baseline, define success criteria.
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: