Skip to content
Back to skills

Project Plan

ASecurity

Turn a product goal or feature request into a clear Agiflow project plan with small, testable tasks in Planning status. Use when starting a project, decomposing a feature, clarifying requirements, or converting an idea into an actionable backlog.

  • 3 stars
  • 0 votes
  • 0 copies
  • 4 views
  • Added September 12, 2026
ai-agentsgogit

Security analysis

A100/100

Scanned September 12, 2026

npx -y skills add thedixitjain/the-mega-skill-library --skill project-plan --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Project Plan?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Project Plan
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/thedixitjain-project-plan/badge)](https://www.skillsdirectory.com/skills/thedixitjain-project-plan)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: project-plan
description: "Turn a product goal or feature request into a clear Agiflow project plan with small, testable tasks in Planning status. Use when starting a project, decomposing a feature, clarifying requirements, or converting an idea into an actionable backlog."
category: ai-agents-and-harness
source_repo: hashgraph-online/awesome-codex-plugins
source_path: "plugins/AgiFlow/ai-plugin/skills/project-plan/SKILL.md"
source_url: https://github.com/hashgraph-online/awesome-codex-plugins/blob/HEAD/plugins/AgiFlow/ai-plugin/skills/project-plan/SKILL.md
---


# Agiflow Project Plan

Create a focused near-term plan. Plan tasks first and leave work-unit creation to backlog grooming.

## Workflow

1. Call `get_current_scope` and resolve the target project with `list_projects` when needed.
2. Call `get_project_detail`, `list_project_statuses`, and `list_tasks` to understand goals, configured statuses, and existing work.
3. Ask only the questions needed to resolve the intended outcome, users, scope, constraints, and definition of done.
4. Check for duplicate or overlapping tasks before proposing new ones.
5. Decompose the outcome into small vertical slices that can be completed and verified independently.
6. For each proposed task, include:
   - Clear title
   - Outcome-focused description
   - At least two testable acceptance criteria
   - Explicit in-scope and out-of-scope boundaries
   - Priority and useful categorization tags
   - Dependencies or sequencing notes when relevant
7. Present the complete task plan and request approval before writing.
8. After approval, use `batch_create_tasks` for multiple tasks or `create_task` for one task. Use the exact Planning status name returned by `list_project_statuses`.
9. Call `list_tasks` to verify the created tasks and report any per-item errors.

## Planning Rules

- Do not create work units in this workflow.
- Do not promote tasks to Todo.
- Prefer the smallest plan that delivers useful progress.
- Split tasks that combine unrelated outcomes or cannot be verified independently.
- Preserve existing work and avoid duplicates.

## Response

Report created task titles, priorities, dependencies, and any tasks that still need user decisions. Recommend `refine-task` for ambiguous tasks or `backlog-grooming` when the Planning backlog is ready.

---

**Source:** [`hashgraph-online/awesome-codex-plugins`](https://github.com/hashgraph-online/awesome-codex-plugins) → `plugins/AgiFlow/ai-plugin/skills/project-plan/SKILL.md`

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.