CCPM Project Management
automazeio/ccpm
Runs a spec-driven workflow from PRD to epic to GitHub issues to parallel agents, with status, standup and blocked-work reports from bundled scripts.
Manage technical projects from initiation through delivery and closure: choose and tailor predictive, iterative, Scrum, flow-based, or hybrid approaches; coordinate teams and vendors; track…
Install Technical Project Management
$ npx skills add magnus919/agent-skills --skill technical-project-management -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install magnus919/agent-skills technical-project-management --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/magnus919/agent-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/technical-project-management .claude/skills/technical-project-management && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "technical-project-management" agent skill from https://github.com/magnus919/agent-skills/tree/main/technical-project-management into .claude/skills/technical-project-management/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "technical-project-management", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/magnus919/agent-skills/tree/main/technical-project-managementType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add magnus919/agent-skills --skill technical-project-management -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install magnus919/agent-skills technical-project-management --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/magnus919/agent-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/technical-project-management .agents/skills/technical-project-management && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "technical-project-management" agent skill from https://github.com/magnus919/agent-skills/tree/main/technical-project-management into .agents/skills/technical-project-management/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "technical-project-management", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add magnus919/agent-skills --skill technical-project-management -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install magnus919/agent-skills technical-project-management --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/magnus919/agent-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/technical-project-management .cursor/skills/technical-project-management && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "technical-project-management" agent skill from https://github.com/magnus919/agent-skills/tree/main/technical-project-management into .cursor/skills/technical-project-management/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "technical-project-management", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/magnus919/agent-skills.git --path technical-project-management--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add magnus919/agent-skills --skill technical-project-management -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install magnus919/agent-skills technical-project-management --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/magnus919/agent-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/technical-project-management .gemini/skills/technical-project-management && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "technical-project-management" agent skill from https://github.com/magnus919/agent-skills/tree/main/technical-project-management into .gemini/skills/technical-project-management/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "technical-project-management", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install magnus919/agent-skills technical-project-managementInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add magnus919/agent-skills --skill technical-project-management -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/magnus919/agent-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/technical-project-management .github/skills/technical-project-management && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "technical-project-management" agent skill from https://github.com/magnus919/agent-skills/tree/main/technical-project-management into .github/skills/technical-project-management/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "technical-project-management", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add magnus919/agent-skills --skill technical-project-management -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install magnus919/agent-skills technical-project-management --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/magnus919/agent-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/technical-project-management .opencode/skills/technical-project-management && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "technical-project-management" agent skill from https://github.com/magnus919/agent-skills/tree/main/technical-project-management into .opencode/skills/technical-project-management/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "technical-project-management", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
technical-project-management- GitHub stars
- 115
- Token cost
- ~2.9k tokens
- SKILL.md length
- 1,108 words
- Files
- 38 (incl. scripts, references)
- Skills in repo
- 131
- Repo updated
- First seen
- Licence
- MIT
At a glance
Manage technical projects from initiation through delivery and closure: choose and tailor predictive, iterative, Scrum, flow-based, or hybrid approaches; coordinate teams and vendors; track…
- Works in 6 steps: Establish mandate and authority;… → Select the smallest adequate management… → Reuse the implementation plan and… → …
- A team has no project manager
- SKILL.md covers First move, Operating loop, Reference routing and Templates and calculation, plus 2 more sections
- Calls python3
What it does
Technical Project Management is an agent skill from magnus919/agent-skills. Manage technical projects from initiation through delivery and closure: choose and tailor predictive, iterative, Scrum, flow-based, or hybrid approaches; coordinate teams and vendors; track milestones, risks, issues, dependencies, forecasts, scope changes, and recovery. Use when a team has no project manager, a TPM needs decision-ready analysis, a project is slipping, or commitments and handoffs need coordination. Use technical-program-management instead when multiple related projects, teams, vendors, shared…
Its SKILL.md is about 2.9k tokens, which your agent loads only when the skill is triggered. The skill folder holds 40 other files, including scripts and reference files (for example `README.md`, `evals/evals.json` and `evals/sample-review.md`). Compatibility notes: Host-neutral methodology and Markdown templates. Optional read-only schedule analysis requires Python 3.10+ standard library; no credentials or network.
It sits in Product & Project Management, covering Project management. The repository describes itself as: Curated collection of AI agent skills for Hermes and other agent frameworks. The licence is MIT.
When your agent uses it
- A team has no project manager
- A TPM needs decision-ready analysis
- A project is slipping
- Commitments and handoffs need coordination
Example prompts
- “/technical-project-management”
Requirements
- Python 3
- Compatibility (from SKILL.md): Host-neutral methodology and Markdown templates. Optional read-only schedule analysis requires Python 3.10+ standard library; no credentials or network.
Workflow steps
6 steps, taken from the first numbered list in SKILL.md.
- Establish mandate and authority; separate approved commitments, forecasts,
- Select the smallest adequate management approach. Preserve effective existing
- Reuse the implementation plan and maintain milestones, dependency commitments,
- Compare evidence with the baseline and tolerances. Investigate contradictions;
- Present feasible options when scope, capacity, cost, or dates conflict. Keep the
- Close only on acceptance and explicit residual ownership. Distinguish project
What it can do on your machine
Read from SKILL.md and the folder at commit 22b4723. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships 1 file in scripts/, which the agent can run.
Shell commands in SKILL.md call:
python3
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Compatibility
Host-neutral methodology and Markdown templates. Optional read-only schedule analysis requires Python 3.10+ standard library; no credentials or network.
From compatibility in the SKILL.md frontmatter.
Context cost
Technical Project Management loads about 2.9k tokens when it runs, and up to ~16k if it reads all its reference files. Until then it costs about 221 tokens; SKILL.md has 1,108 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.
SKILL.md
The full file from magnus919/agent-skills at commit 22b4723, republished under its MIT licence (© magnus919). 1,108 words, ~2,944 tokens.
Download SKILL.mdSave it as
.claude/skills/technical-project-management/SKILL.md (or your agent's skills folder). This skill also uses 37 other files; get the full folder from GitHub.- name
- technical-project-management
- description
- Manage technical projects from initiation through delivery and closure: choose and tailor predictive, iterative, Scrum, flow-based, or hybrid approaches; coordinate teams and vendors; track milestones, risks, issues, dependencies, forecasts, scope changes, and recovery. Use when a team has no project manager, a TPM needs decision-ready analysis, a project is slipping, or commitments and handoffs need coordination. Use `technical-program-management` instead when multiple related projects, teams, vendors, shared capacity, or benefits must be coordinated toward one outcome. Adapt depth to the user's expertise. Do not use for a standalone coding task, product discovery or strategy, only writing an implementation plan, only diagnosing Kanban flow, operating a ticket tool, incident command, or a release go/no-go decision; route those to specialists.
- compatibility
- Host-neutral methodology and Markdown templates. Optional read-only schedule analysis requires Python 3.10+ standard library; no credentials or network.
- license
- MIT
Technical Project Management
Help a team make and maintain credible delivery commitments. Start at the user's current decision; do not restart a healthy project or impose a new methodology.
First move
Read existing project artifacts before asking questions. Identify the outcome, current phase, immediate decision, decision-maker, constraints, and evidence gaps. Infer experience from the request and artifacts; ask about preference only if it matters. For teams without a PM, provide a small usable working system and explain unfamiliar concepts in context. For experienced TPMs, lead with the delta, options, recommendation, and decision needed; omit introductory lessons.
Choose the entry point
| Starting condition | First action | Primary output |
|---|---|---|
| New or inherited project with unclear mandate | Read Engagement and initiation | Proposed brief with authority and evidence gaps |
| Approved work with a delivery method but weak control | Read Control and communication | Current control record and decision brief |
| Slipping date, cost, scope, or dependency | Read Forecasting and schedule analysis and Change and recovery | Conditional forecast and recovery options |
| Cross-team, supplier, or mixed-method handoff | Read Hybrid and dependencies | Dependency agreement and acceptance evidence |
| Delivered work, retirement, or decommissioning with unresolved ownership or benefits | Read Closure and transition | Conditional closure, accepted transition, or decommissioning record |
| Technical uncertainty needs staged learning | Read Adaptive delivery | Evidence-backed decision among PoC, prototype, pilot, or stop; none alone proves production readiness |
| Forecast, deadline, or resource-feasibility question | Read Forecasting and schedule analysis | Conditional forecast stating model, assumptions, capacity, and feasibility limits |
| Material risk, issue, assumption, or decision needs control | Read Control and communication | Record with owner, signal/trigger, response, authority, and next review |
| A supplier or team handoff lacks readiness or acceptance evidence | Read Hybrid and dependencies | Agreement with provider, receiver, definition of ready, evidence, fallback, and escalation |
Do not call a desired date a commitment, a forecast an acceptance, or a diagnostic brief an approved plan.
Before proposing a commitment, identify who can authorize scope, dates, capacity, acceptance, and external communication. Mark each as accepted, proposed, unknown, or disputed. Read-only diagnosis may proceed; external updates require authorization.
Operating loop
- Establish mandate and authority; separate approved commitments, forecasts, assumptions, and unknowns. A diagnostic or options brief can precede approval; do not turn it into an approved implementation plan.
- Select the smallest adequate management approach. Preserve effective existing practices and specify any changed decision rights, cadence, and handoffs.
- Reuse the implementation plan and maintain milestones, dependency commitments, remaining work, resource availability, risks, issues, and decisions.
- Compare evidence with the baseline and tolerances. Investigate contradictions; missing evidence means unknown, not green. Surface forecast changes immediately when material; do not wait for a scheduled report.
- Present feasible options when scope, capacity, cost, or dates conflict. Keep the baseline history; an authorized change is not permission to hide prior variance.
- Close only on acceptance and explicit residual ownership. Distinguish project closure, release readiness, service operation, and later benefit realization.
Reference routing
Read only what the current task requires. Each reference includes applicability, procedures, failure signals, and an observable exit.
A multi-project initiative with a shared outcome, cross-project dependencies, or
program-level benefits belongs to technical-program-management; a single bounded
project remains here.
| Decision phase / situation | Read | Exit artifact or evidence |
|---|---|---|
| New or inherited project, no PM, expert collaboration | Engagement and initiation | Proposed brief with mandate, authority, and evidence gaps |
| Choosing or questioning a methodology | Method selection | Approach decision with adaptations and revisit trigger |
| Predictive planning, stages, tolerances, fixed constraints | Predictive and stage governance | Baseline, tolerances, and gate evidence |
| Scrum, iteration, incremental delivery, discovery uncertainty | Adaptive delivery | Learning/increment evidence and inspect/adapt decision |
| Flow, shared specialists, critical chain, appetite-based work | Flow and constrained capacity | Capacity/WIP or appetite decision with owner |
| Mixed methods, cross-team or vendor interfaces | Hybrid and dependencies | Dependency agreement and interface acceptance evidence |
| Estimates, forecasts, budgets, schedule model | Forecasting and schedule analysis | Conditional forecast with assumptions and feasibility limits |
| Weekly control, stakeholder disagreement, escalations | Control and communication | Status/update or decision brief with next checkpoint |
| Scope changes, troubled projects, recovery | Change and recovery | Change/recovery record preserving the baseline |
| Acceptance, cancellation, operational handoff | Closure and transition | Closure or transition record with residual owners |
| Real examples or transferability checks | Case studies | Source-limited analogy, not a guarantee |
| Research provenance, edition, evidence limits | Source index | Traceable evidence ledger |
| Skill purpose, coverage, research decisions | Research brief | Coverage and limitation record |
| Validation scope and behavioral evaluation protocol | Evaluation guide | Reproducible evaluation record |
Show full SKILL.md (387 more words)Show less
Templates and calculation
Adapt existing project documents rather than creating parallel sources of truth. Use only artifacts that answer a current decision.
| Need | Artifact |
|---|---|
| Establish mandate and working agreements | Project brief |
| Explain method choice and adaptation | Approach decision |
| Maintain milestones and evidence | Project control record |
| Coordinate a supplier or receiving team | Dependency agreement |
| Report a change and ask for a decision | Status and decision brief |
| Assess scope changes or recovery options | Change and recovery record |
| Accept, cancel, or transfer ownership | Closure record |
| Calculate a small dependency network | Example schedule |
Run python3 scripts/schedule.py --input templates/schedule-example.json --json
from this skill's directory when dependency arithmetic helps. Read forecasting
first: the result is an unconstrained earliest schedule, not a commitment or a
resource-leveled plan. The script only reads input and writes stdout/stderr.
Run python3 -m unittest discover -s scripts -p 'test_*.py' for its tests.
When not to use
- A coding fix or architecture design: use the applicable engineering skill.
- Validating needs or choosing product investments: use product-discovery or product-roadmapping-and-portfolio.
- Only decomposing an approved requirement: use implementation-planning.
- Detailed board, WIP, or service-flow diagnosis: use kanban-guru.
- Shaping a bounded product bet: use product-shaping.
- Product-wide decision rights: use product-operations-and-governance.
- Executive-office support: use chief-of-staff-methodology.
- Release mechanics or launch approval: use release-engineering and production-readiness. This skill may track project implications after that decision, but does not approve the release.
- Live incident command: use site-reliability-engineering.
- Ticket operations alone: use jira or linear. Use financial-modeling for financial model construction, and legal-strategy for contract interpretation.
Authority and completion
This methodology prepares decisions. It does not invent stakeholder consent, assign accepted commitments on someone else's behalf, or approve risk. Updating external project systems or sending communications changes external state:
Confirm the target, scope, and rollback path before acting. Read-only discovery may proceed without confirmation.
Apply existing session authorization; do not ask repeatedly for the same scope. Destructive actions need an explicit directive. Keep prepared drafts visibly distinct from issued communications. Do not monitor people or turn activity counts into individual performance judgments.
Complete a requested management cycle when the artifact or update is delivered, claims have evidence or explicit uncertainty, and unresolved decisions have an accountable route and next review trigger. Do not imply ongoing monitoring without an authorized mechanism. If three diagnostic passes yield no new evidence, stop with the missing input and affected decision; do not manufacture certainty.
© magnus919, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 37 other files (scripts, references) in technical-project-management of magnus919/agent-skills.
- SKILL.md
- README.md
- evals/evals.json
- evals/sample-review.md
- evals/samples/baseline-expert.md
- evals/samples/baseline-schedule.md
- evals/samples/baseline-team.md
- evals/samples/final-team-provenance.json
- evals/samples/final-team.md
- evals/samples/with-skill-expert.md
- evals/samples/with-skill-schedule.md
- evals/samples/with-skill-team.md
- references/adaptive-delivery.md
- references/case-studies.md
- references/change-and-recovery.md
- references/closure-and-transition.md
- references/control-and-communication.md
- references/engagement-and-initiation.md
- … and 20 more
Open the folder on GitHubat commit 22b4723
Compare with similar skills
Technical Project Management next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Technical Project Management this skillmagnus919/agent-skills | 115 | — | ~2.9k | Automated safety check: Pass | MIT | |
| CCPM Project Managementautomazeio/ccpm | 8.4k | — | ~1.1k | Automated safety check: Pass | MIT | |
| Uvastral-sh/claude-code-plugins | 313 | 2 repos | ~980 | Automated safety check: Pass | Apache-2.0 | |
| Project Managementkunchenguid/firstmate | 7.8k | — | ~2.1k | Automated safety check: Pass | MIT | |
| Hivemind Goalsactiveloopai/hivemind | 1.6k | — | ~1.7k | Automated safety check: Notes | Apache-2.0 | |
| Ichartjswanghetommy/ichartjs | 352 | — | ~4.3k | Automated safety check: Pass | Apache-2.0 |
Similar skills
- Official
Uv
astral-sh/claude-code-plugins
Guide for using uv, the Python package and project manager. An agent skill from astral-sh/claude-code-plugins.
Project Management
kunchenguid/firstmate
Agent-only procedure for Firstmate project management. An agent skill from kunchenguid/firstmate.
Hivemind Goals
activeloopai/hivemind
Create, track and update team goals via the Deeplake virtual filesystem at memory/goal/.
Ichartjs
wanghetommy/ichartjs
Plan, validate, render, explain, and safely edit iChart.js visualizations from tabular, project, or diagram data.
Hivemind Goals
activeloopai/hivemind
Create, track and update team goals in Hivemind via the hivemind CLI.
More from magnus919/agent-skills
All 131 skills in this repoArtifact Pyramids
magnus919/agent-skills
Organize durable agent research outputs as summaries, analysis, and evidence dossiers.
Ascii City Engine
magnus919/agent-skills
Build portable, first-person colored ASCII city engines and small GIS-derived city packs.
Color Management
magnus919/agent-skills
Manage color workflows with ICC profiles, working spaces, gamut mapping, and color science.
Data Scientist
magnus919/agent-skills
A skill your agent uses for PhD-level expertise in data science, statistics, and machine learning: rigorous statistical analysis, experimental design, causal inference, advanced modeling, research…
Docker Compose
magnus919/agent-skills
Use Docker Compose to define, run, debug, and harden multi-container applications.
Fpga Development
magnus919/agent-skills
Design, review, simulate, and verify FPGA logic using explicit RTL contracts, clock and reset models, CDC analysis, timing constraints, and reproducible implementation evidence.
Related
Categories
Questions about Technical Project Management
What does Technical Project Management do?
Manage technical projects from initiation through delivery and closure: choose and tailor predictive, iterative, Scrum, flow-based, or hybrid approaches; coordinate teams and vendors; track…. Technical Project Management is an agent skill from magnus919/agent-skills. Manage technical projects from initiation through delivery and closure: choose and tailor predictive, iterative, Scrum, flow-based, or hybrid approaches; coordinate teams and vendors; track milestones, risks, issues, dependencies, forecasts, scope changes, and recovery.
When should I use Technical Project Management?
Technical Project Management fits situations like: A team has no project manager; A TPM needs decision-ready analysis; A project is slipping; commitments and handoffs need coordination.
How do I install Technical Project Management in Claude Code?
Run `npx skills add magnus919/agent-skills --skill technical-project-management -a claude-code`. Or copy the skill folder (technical-project-management in magnus919/agent-skills) into .claude/skills/technical-project-management in your project. Claude Code loads it when a task matches its description.
How do I install Technical Project Management in Codex?
Run `npx skills add magnus919/agent-skills --skill technical-project-management -a codex`. Or copy the skill folder (technical-project-management in magnus919/agent-skills) into .agents/skills/technical-project-management in your project. Codex loads it when a task matches its description.
Can I use Technical Project Management in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add magnus919/agent-skills --skill technical-project-management -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/technical-project-management, .gemini/skills/technical-project-management, .github/skills/technical-project-management and .opencode/skills/technical-project-management in your project.
What does Technical Project Management need to run?
Going by SKILL.md and its folder, Technical Project Management needs the command-line tools its instructions call (python3). Our summary lists: Python 3. Compatibility (from SKILL.md): Host-neutral methodology and Markdown templates. Optional read-only schedule analysis requires Python 3.10+ standard library; no credentials or network..
Does Technical Project Management access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Technical Project Management safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does Technical Project Management use?
Technical Project Management is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Technical Project Management use?
About 2.9k tokens (SKILL.md is roughly 12k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 13k tokens, read only when the agent opens those files.
What are the alternatives to Technical Project Management?
Skills that share tags, products or a category with Technical Project Management: CCPM Project Management (automazeio/ccpm, 8.4k stars), Uv (astral-sh/claude-code-plugins, 313 stars), Project Management (kunchenguid/firstmate, 7.8k stars) and Hivemind Goals (activeloopai/hivemind, 1.6k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Technical Project Management?
magnus919 (a GitHub user) maintains it in magnus919/agent-skills, which has 115 GitHub stars. The repository holds 131 skills in this directory. The repository was last updated on October 10, 2026.
Source: magnus919/agent-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.