apm_complexity
Analyze task complexity, generate expansion recommendations, and create reports
LABSCO SUMMARY
It tells you the interview will take minutes, and asks you to say so.
apm_project_brief_create and both of its polling tools carry the same instruction — task generation is long-running, and the user should be told to be patient — which is a small piece of interface design doing real work, because a silent multi-minute wait is where people abandon a tool and start again. The complexity analysis is the distinctive capability: rather than only tracking tasks, it says which ones are too large and recommends how to break them down. The Context7 pair rides along as a separate capability, and its ordering constraint is stated plainly — resolve the library ID first, because the documentation tool will not accept a bare package name.
What it is
A project management server built around an artifacts file, with an interview-driven brief, task and dependency tools, complexity analysis, and library documentation retrieval.
What you get
- apm_task for querying and managing tasks by status, priority, ID or containing text, with or without subtasks
- apm_task_modify for creating, updating and deleting tasks and subtasks, with a research flag, a threshold, and confirm and force options
- apm_task_generate, writing individual task files into the artifacts directory from artifacts.json
- A project brief created through an interactive interview run in stages with a session ID and a maximum task count — its own description warns that task generation is long-running and asks you to tell the user so
- apm_project_brief_status and apm_project_brief_result, polling that operation and collecting its output once it completes
- apm_dependencies, adding and managing dependencies between tasks
- apm_complexity, analysing task complexity, producing expansion recommendations and writing a report, with a research option, a threshold and markdown output
- context7_library_id and context7_library_docs, resolving a package name into a Context7 library ID and then fetching current documentation for it by topic
Requirements
A project root in PROJECT_ROOT, an Anthropic API key in ANTHROPIC_API_KEY, and a Perplexity API key in PERPLEXITY_API_KEY.
Setup effort
One command plus a key — npx -y @gannonh/agent-pm@latest, then supply credentials
USE CASES
01
Getting from a written brief to a task tree
The interview runs as a long operation: create it, poll the status, then collect the result once generation has finished. Generating the task files turns whatever came back into one file per task under apm-artifacts.
02
Deciding which tasks are too big to start
Complexity analysis returns expansion recommendations against a threshold and writes a report; the modify tool then splits the tasks it flagged into subtasks, with a research mode when the split needs outside context.
03
Keeping the order of work honest
Dependencies are edges you add, remove and validate rather than a field you remember to fill in, and the query tool reads the backlog back by status, priority or contained text with subtasks attached.
04
Checking a library's current API mid-task
Resolve the package name to a Context7 library id first — the docs tool will not take a bare name — then fetch documentation narrowed to the topic you are implementing.
10 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
apm_dependencies
Manage task dependencies
apm_project_brief_create
Create a project brief through an interactive interview process and generate tasks. IMPORTANT: Task generation is a long-running operation that may take several minutes to complete. Always inform users to be patient when this operation is in progress.
apm_project_brief_result
Get the result of a completed project brief interview operation. Call this after apm_project_brief_status indicates the operation is complete. If the operation is still running, inform users to be patient as task generation can take several minutes.
apm_project_brief_status
Get the status of a project brief interview operation. IMPORTANT: If the status is "running", remind users that the operation may take several minutes to complete, especially for task generation.
apm_task
Manage and query tasks in the project
apm_task_generate
Generates individual task files in apm-artifacts directory based on artifacts.json
apm_task_modify
Create, update, and delete tasks and subtasks
context7_library_docs
Fetches up-to-date documentation for a library. You must call 'context7_library_id' first to obtain the exact Context7-compatible library ID required to use this tool.
context7_library_id
Required first step: Resolves a general package name into a Context7-compatible library ID. Must be called before using 'context7_library_docs' to retrieve a valid Context7-compatible library ID.
BEFORE YOU INSTALL
What to know first
Tools you get
10 tools when we connected. context7_library_id and context7_library_docs are available but undocumented. Names with a _node suffix in the documentation's detail sections, such as apm_complexity_node, are stale; the real name is apm_complexity.
Requires
- npx on PATH
- Node.js 20.0.0 or later
- ANTHROPIC_API_KEY in your environment
CONTEXT COST
Light Standing cost
Rated by the size of the 10 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Server setup
TERMINAL
npx -y @gannonh/agent-pm@latestMCP Clients
Cursor
CURSOR · JSON
{
"mcpServers": {
"agent-pm": {
"command": "npx",
"args": [
"-y",
"@gannonh/agent-pm@latest"
],
"env": {
"PROJECT_ROOT": "<YOUR_PROJECT_ROOT>",
"ANTHROPIC_API_KEY": "<YOUR_ANTHROPIC_API_KEY>",
"PERPLEXITY_API_KEY": "<YOUR_PERPLEXITY_API_KEY>"
}
}
}
}Augment
AUGMENT · JSON
{
"augment.advanced": {
"mcpServers": [
{
"name": "agent-pm",
"command": "npx",
"args": [
"-y",
"@gannonh/agent-pm@latest"
],
"env": {
"PROJECT_ROOT": "<YOUR_PROJECT_ROOT>",
"ANTHROPIC_API_KEY": "<YOUR_ANTHROPIC_API_KEY>",
"PERPLEXITY_API_KEY": "<YOUR_PERPLEXITY_API_KEY>"
}
}
]
}
}
