Agent skill

Plan

by mhmzdev in mhmzdev/the-holy-quran-app

Turn an idea or brainstorm into an actionable execution plan for The Holy Qur'an app with phases, file changes, and machine-checkable success criteria.

MITAuto-check passedAgent Workflows

Install Plan

skills CLI

$ npx skills add mhmzdev/the-holy-quran-app --skill plan -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install mhmzdev/the-holy-quran-app plan --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/mhmzdev/the-holy-quran-app.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/plan .claude/skills/plan && rm -rf skills-src

Use ~/.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/

Paste into Claude Code

Install the "plan" agent skill from https://github.com/mhmzdev/the-holy-quran-app/tree/master/.agents/skills/plan into .claude/skills/plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "plan", 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

$skill-installer install https://github.com/mhmzdev/the-holy-quran-app/tree/master/.agents/skills/plan

Type 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.

skills CLI

$ npx skills add mhmzdev/the-holy-quran-app --skill plan -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install mhmzdev/the-holy-quran-app plan --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/mhmzdev/the-holy-quran-app.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/plan .agents/skills/plan && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "plan" agent skill from https://github.com/mhmzdev/the-holy-quran-app/tree/master/.agents/skills/plan into .agents/skills/plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "plan", 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.

skills CLI

$ npx skills add mhmzdev/the-holy-quran-app --skill plan -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install mhmzdev/the-holy-quran-app plan --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/mhmzdev/the-holy-quran-app.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/plan .cursor/skills/plan && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "plan" agent skill from https://github.com/mhmzdev/the-holy-quran-app/tree/master/.agents/skills/plan into .cursor/skills/plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "plan", 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

$ gemini skills install https://github.com/mhmzdev/the-holy-quran-app.git --path .agents/skills/plan

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add mhmzdev/the-holy-quran-app --skill plan -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install mhmzdev/the-holy-quran-app plan --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/mhmzdev/the-holy-quran-app.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/plan .gemini/skills/plan && rm -rf skills-src

Use ~/.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/

Paste into Gemini CLI

Install the "plan" agent skill from https://github.com/mhmzdev/the-holy-quran-app/tree/master/.agents/skills/plan into .gemini/skills/plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "plan", 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.

GitHub CLI

$ gh skill install mhmzdev/the-holy-quran-app plan

Installs 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).

skills CLI

$ npx skills add mhmzdev/the-holy-quran-app --skill plan -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/mhmzdev/the-holy-quran-app.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/plan .github/skills/plan && rm -rf skills-src

Use ~/.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/

Paste into GitHub Copilot

Install the "plan" agent skill from https://github.com/mhmzdev/the-holy-quran-app/tree/master/.agents/skills/plan into .github/skills/plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "plan", 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.

skills CLI

$ npx skills add mhmzdev/the-holy-quran-app --skill plan -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install mhmzdev/the-holy-quran-app plan --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/mhmzdev/the-holy-quran-app.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/plan .opencode/skills/plan && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "plan" agent skill from https://github.com/mhmzdev/the-holy-quran-app/tree/master/.agents/skills/plan into .opencode/skills/plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "plan", 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: plan
GitHub stars: 889
Token cost: ~957 tokens
SKILL.md length: 388 words
Files: 1
Skills in repo: 7
Repo updated: Sep 10, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Turn an idea or brainstorm into an actionable execution plan for The Holy Qur'an app with phases, file changes, and machine-checkable success criteria.

Works in 7 steps: Clear starting point → Targeted research (no full audits) → Name and locate → …
The user says plan this
SKILL.md covers Phase 0 — Clear starting point, Phase 1 — Targeted research…, Phase 2 — Name and locate and Phase 3 — Machine-checkable…, plus 4 more sections
Calls git

What it does

Plan is an agent skill from mhmzdev/the-holy-quran-app. Turn an idea or brainstorm into an actionable execution plan for The Holy Qur'an app with phases, file changes, and machine-checkable success criteria. Use when the user says "plan this", "write a plan", "how should we build X". Writes the plan into docs/exec-plans/backlog/ and registers it in docs/exec-plans/index.md.

Its SKILL.md is about 960 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Agent Workflows, covering Brainstorming, Planning and Cross-platform mobile apps. It works with Flutter and Android. The repository describes itself as: Holy Qur'an application developed via Flutter. The licence is MIT.

When your agent uses it

The user says plan this
How should we build X

Example prompts

“plan this”
“write a plan”
“how should we build X”
“/plan”

Workflow steps

7 steps, taken from the step headings in SKILL.md.

Clear starting point
Targeted research (no full audits)
Name and locate
Machine-checkable success criteria
Write the plan
Register
Handoff (AskUserQuestion)

What it can do on your machine

Read from SKILL.md and the folder at commit 33edb90. 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
Shell commands in SKILL.md call:
- git
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.
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.

Context cost

Plan loads about 957 tokens when it runs. Until then it costs about 81 tokens; SKILL.md has 388 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~81
When it runs · the whole SKILL.md, loaded when a task matches: ~957

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); files beside SKILL.md are not scanned.

SKILL.md

The full file from mhmzdev/the-holy-quran-app at commit 33edb90, republished under its MIT licence (© mhmzdev). 388 words, ~957 tokens.

Download SKILL.mdSave it as .claude/skills/plan/SKILL.md (or your agent's skills folder).

name: plan
description: Turn an idea or brainstorm into an actionable execution plan for The Holy Qur'an app with phases, file changes, and machine-checkable success criteria. Use when the user says "plan this", "write a plan", "how should we build X". Writes the plan into docs/exec-plans/backlog/ and registers it in docs/exec-plans/index.md.
argument-hint: the feature/fix to plan, or a path to a brainstorm doc

Plan

You are turning a WHAT into a HOW. Output is a plan document, not code — precise enough that /build executes it without re-deciding scope.

Repo plan rules (AGENTS.md → Planning): new plans land only in docs/exec-plans/backlog/; always add the row to docs/exec-plans/index.md; /build moves plans backlog/ → active/ → completed/.

Position: /brainstorm → /grill-me → **/plan** → /build → /review.

Phase 0 — Clear starting point

Given a doc path (docs/brainstorm/…), read it and extract settled decisions. Given a bare description, check docs/brainstorm/ and docs/exec-plans/ for a related artifact and offer to use it.
Fuzzy scope or unresolved approaches → stop and recommend /brainstorm, then /grill-me.
Decided but ungrilled and non-trivial (Hive schema, navigation, release, splash preload) → recommend /grill-me first.

Phase 1 — Targeted research (no full audits)

Grep/Glob only what the plan touches. New bloc → read lib/blocs/chapter/ (3 files) + its registration in locator.dart/app.dart + test/blocs/chapter_bloc_test.dart. New screen → read the closest screen folder + router.dart/routes.dart + its widget test. Data change → packages/al_quran_api/lib/src/data_providers/impls/… and the model + docs/architecture/data-layer.md.
Note exact paths and line refs you'll change.
Pull conventions from .agents/rules/ and docs/conventions/.
Risk areas (Hive typeIds/fields, permissions, versioning, anything users' cached data depends on) → cite the doc and flag the risk in the plan.

Phase 2 — Name and locate

Title in conventional-commit form (feat:, fix:, refactor:, chore:). File: docs/exec-plans/backlog/<kebab-topic>.md, no date prefix.

Show full SKILL.md (173 more words)Show less

Phase 3 — Machine-checkable success criteria

Each criterion carries exactly one verify::

verify: fvm flutter analyze / fvm flutter test / fvm flutter test test/blocs/x_bloc_test.dart
verify: cd packages/al_quran_api && fvm dart run build_runner build (after model changes; then git diff --stat shows regenerated files)
verify: fvm flutter build apk --release (for anything touching Android/Gradle/pubspec)
verify: manual <numbered steps> when no command exists (e.g. airplane-mode launch shows cached surahs). Rewrite any vacuous criterion into something provable.

Phase 4 — Write the plan

OKF frontmatter (type: Plan, title, description, tags, timestamp, status: backlog) then:

markdown

# <conventional-commit title>
## Problem
## Approach
(prose; which existing patterns it reuses; layer boundaries respected)
## Success criteria
- [ ] <criterion> — `verify: <command>`
## Phases
### Phase 1 — <name>
**Status:** Not started
- Files: …
- Tests: …
## Risks & open questions
## Out of scope

Sizing: one phase ≈ one context window. Build order Model → DataProvider → Repo → Bloc → UI. Include the build_runner step when models change. Note a split boundary if too big for one PR.

Phase 5 — Register

Add a Backlog row to docs/exec-plans/index.md and a line to docs/log.md.

Phase 6 — Handoff (AskUserQuestion)

Build it now (/build) · Refine (/refine-approach) · Grill it first (/grill-me) · Leave in backlog.

What NOT to do

Don't write code. Don't put the plan anywhere but backlog/. Don't date-prefix. Don't invent unverifiable criteria. Don't re-audit the whole codebase.

Files

Just SKILL.md in .agents/skills/plan of mhmzdev/the-holy-quran-app.

Open the folder on GitHubat commit 33edb90

Compare with similar skills

Plan 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.

Plan compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Plan this skillmhmzdev/the-holy-quran-app	889	—	~957	Automated safety check: Pass	MIT	27 days ago
Skill CreatorChevey339/kelivo	4.2k	—	~1.3k	Automated safety check: Pass	AGPL-3.0	today
Retrieving Developer Knowledgegoogle/skills	21k	—	~2k	Automated safety check: Pass	Apache-2.0	today
Frb Android Emulator Preparefzyzcjy/flutter_rust_bridge	5.4k	—	~2.1k	Automated safety check: Notes	MIT	yesterday
Claude Android NinjaDrjacky/claude-android-ninja	124	—	~5.2k	Automated safety check: Pass	Apache-2.0	8 days ago
Web3authWeb3Auth/web3auth-examples	144	—	~1.4k	Automated safety check: Pass	MIT	4 days ago

Similar skills

Skill Creator
Chevey339/kelivo
Create or improve skills, turn a conversation into reusable SKILL.md instructions, and validate their behavior.
4.2k GitHub stars~1.3k tokensUpdated today
Agent WorkflowsAuto-check passed
Retrieving Developer Knowledge
google/skills
Official
Searches, retrieves, and synthesizes official Google developer documentation across Google Cloud, AI/Gemini, Android, Chrome, Web, Flutter, Go, Firebase, and other Google developer platforms.
21k GitHub stars~2k tokensUpdated today
Backend & APIsAuto-check passed
Frb Android Emulator Prepare
fzyzcjy/flutter_rust_bridge
A skill your agent uses when preparing, installing, diagnosing, or explaining the host Android Emulator environment for flutterrustbridge local runtime validation, including Android SDK command-line…
5.4k GitHub stars~2.1k tokensUpdated yesterday
MobileAuto-check: notes
Claude Android Ninja
Drjacky/claude-android-ninja
Build and migrate Android apps with Kotlin, Jetpack Compose, MVVM, Hilt, Room 3 (KSP, SQLiteDriver, Flow/suspend DAOs), Navigation3, and multi-module Gradle.
124 GitHub stars~5.2k tokensUpdated 8 days ago
MobileAuto-check passed
Web3auth
Web3Auth/web3auth-examples
Integrates MetaMask Embedded Wallets (Web3Auth) for non-custodial wallets via social login or custom JWT (Firebase, Auth0, Cognito).
144 GitHub stars~1.4k tokensUpdated 4 days ago
Backend & APIsAuto-check passed
Simdeck
NativeScript/SimDeck
A skill your agent uses for simulator lifecycle, app install/launch, live viewing, UI inspection, touch/keyboard automation, screenshots, recordings, logs, pasteboard, hardware controls, and…
152 GitHub stars~3.6k tokensUpdated 26 days ago
MobileAuto-check passed

Questions about Plan

What does Plan do?

Turn an idea or brainstorm into an actionable execution plan for The Holy Qur'an app with phases, file changes, and machine-checkable success criteria. Plan is an agent skill from mhmzdev/the-holy-quran-app. Turn an idea or brainstorm into an actionable execution plan for The Holy Qur'an app with phases, file changes, and machine-checkable success criteria.

When should I use Plan?

Plan fits situations like: the user says plan this; how should we build X.

How do I install Plan in Claude Code?

Run `npx skills add mhmzdev/the-holy-quran-app --skill plan -a claude-code`. Or copy the skill folder (.agents/skills/plan in mhmzdev/the-holy-quran-app) into .claude/skills/plan in your project. Claude Code loads it when a task matches its description.

How do I install Plan in Codex?

Run `npx skills add mhmzdev/the-holy-quran-app --skill plan -a codex`. Or copy the skill folder (.agents/skills/plan in mhmzdev/the-holy-quran-app) into .agents/skills/plan in your project. Codex loads it when a task matches its description.

Can I use Plan 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 mhmzdev/the-holy-quran-app --skill plan -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/plan, .gemini/skills/plan, .github/skills/plan and .opencode/skills/plan in your project.

What does Plan need to run?

Going by SKILL.md and its folder, Plan needs the command-line tools its instructions call (git).

Does Plan access the network?

SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Plan 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. Review the folder before installing.

What licence does Plan use?

Plan is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Plan use?

About 957 tokens (SKILL.md is roughly 3.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Plan?

Skills that share tags, products or a category with Plan: Skill Creator (Chevey339/kelivo, 4.2k stars), Retrieving Developer Knowledge (google/skills, 21k stars), Frb Android Emulator Prepare (fzyzcjy/flutter_rust_bridge, 5.4k stars) and Claude Android Ninja (Drjacky/claude-android-ninja, 124 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Plan?

mhmzdev (a GitHub user) maintains it in mhmzdev/the-holy-quran-app, which has 889 GitHub stars. The repository holds 7 skills in this directory. The repository was last updated on September 10, 2026.

Source: mhmzdev/the-holy-quran-app on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Plan

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Plan

Phase 0 — Clear starting point

Phase 1 — Targeted research (no full audits)

Phase 2 — Name and locate

Phase 3 — Machine-checkable success criteria

Phase 4 — Write the plan

Phase 5 — Register

Phase 6 — Handoff (AskUserQuestion)

What NOT to do

Files

Compare with similar skills

Similar skills

More from mhmzdev/the-holy-quran-app

Related

Questions about Plan