بنقرة واحدة
using-hyper
Use when starting any conversation - establishes skill selection and the local task-doc workflow
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
القائمة
Use when starting any conversation - establishes skill selection and the local task-doc workflow
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use when shaping a feature before implementation - turns rough ideas into an approved markdown spec and local task directory
Use to execute an approved local markdown task directory iteratively - work the current Now slice, update docs, then stop
Use when implementation is complete and verified - delete finished local task docs, present integration options, and clean up safely
Use for advanced markdown task-doc operations - split work, reprioritize slices, delete finished local task dirs, and keep docs clean
Use after executing a task directory - verifies implementation against plan.md, acceptance checks, and anti-goals
Use before claiming work complete, fixed, or passing - requires fresh evidence before any completion claim
| name | using-hyper |
| description | Use when starting any conversation - establishes skill selection and the local task-doc workflow |
<codex_compat> This skill was ported from Claude Code. In Codex:
SKILL.md from disk.spawn_agent (dispatch in parallel when needed).<skill_overview> Skills are mandatory when they apply, and substantial work must stay grounded in local task docs. </skill_overview>
<rigidity_level>
HIGH FREEDOM - The meta-process is rigid: check for skills, read them from disk, announce usage, and keep work anchored in plans/active/.
</rigidity_level>
<quick_reference>
SKILL.md from disk.plans/active/<slug>/.plan.md, context.md, and tasks.md current.
</quick_reference><when_to_use>
<the_process>
For features, rewrites, and multi-step tasks:
brainstorming shapes the workwriting-plans distills it into task docsexecuting-plans implements the current Now sliceUse:
plans/active/<slug>/plan.mdplans/active/<slug>/context.mdplans/active/<slug>/tasks.mdThese task directories are local working state. Delete the finished directory instead of archiving it.
plan.md is the approved intent and acceptance contractcontext.md is the living discovery logtasks.md is the rolling execution backlogUse verification-before-completion before any completion claim.
</the_process>