neodejack
10 verified skills10 total stars
create-architecture-md
Generate or refresh an `ARCHITECTURE.md` for the current repository. Use when the user asks to create, write, regenerate, or update repository architecture documentation, a code map, or a high-level structural guide that helps contributors answer "where does X live?".
development1
create-execplan
Create a repository-local ExecPlan from an explicitly requested purpose using the bundled PLANS.md guidance. Use only when the user explicitly invokes this skill with phrasing like `use create-execplan for ...`, `use $create-execplan to ...`, or `use the create-execplan skill ...`; do not use implicitly for general planning, task breakdown, product specs, or implementation requests.
testing1
build-from-exec-plan
Build a repository-local feature by executing an existing ExecPlan. Use when the user explicitly asks to build a named plan, for example `use the build-from-exec-plan skill to build multi-cluster-profiles`. Resolve the plan by basename under `docs/exec-plans/`, treat the plan file as the source of truth, move the plan to `docs/exec-plans/active/` before implementation if needed, execute it milestone by milestone with verification, create a git commit after each completed milestone, and move the plan to `docs/exec-plans/completed/` when all milestones are finished.
development1
update-brew-formula
Update a Homebrew tap formula to the latest GitHub Release assets using gh CLI, including verifying the tap repo, locating the formula, computing sha256 for release binaries, and committing/pushing changes. Use when asked to bump a Homebrew formula version to the latest release in a personal tap.
tools1
create-execplan-with-slicing-method
Create a repository-local ExecPlan from an explicitly requested purpose using the bundled PLANS.md guidance, with explicit dependency-graph and vertical-slicing rules applied to milestone decomposition. Use only when the user explicitly invokes this skill with phrasing like `use create-execplan-with-slicing-method for ...` or `use the create-execplan-with-slicing-method skill ...`; do not use implicitly for general planning, task breakdown, product specs, or implementation requests.
testing1
writing-elixir-docs
Write documentation for Elixir modules, functions, types, and callbacks following official Elixir conventions. Use when asked to document Elixir code, add @moduledoc/@doc/@typedoc, write doctests, or improve Elixir documentation. Triggers on: document this elixir module, add elixir docs, write moduledoc, add doctests.
development1
harness-bootstrap
Bootstrap or improve harness-engineering scaffolding for an existing software repository so agents can work safely and productively. Use when asked to make a repo more agent-friendly, adopt harness engineering, prepare a codebase for Codex or mixed human and agent coding, add or improve repo-local guidance such as `AGENTS.md` or `ARCHITECTURE.md`, establish canonical setup/lint/typecheck/test commands, or audit a repository for missing agent workflows and verification rails.
development1
writing-justfiles
Create, edit, and maintain `justfile` automation for any codebase using the `just` command runner. Trigger whenever a request involves creating a new `justfile`, modifying/updating an existing `justfile`, adding or changing recipes, refactoring `justfile` structure, or automating project commands via `just`.
tools1
build-from-exec-plan-hitl
Build a repository-local feature by executing an existing ExecPlan. Use when the user explicitly asks to build a named plan, for example `use the build-from-exec-plan-hitl skill to build multi-cluster-profiles`. Resolve the plan by basename under `docs/exec-plans/`, treat the plan file as the source of truth, move the plan to `docs/exec-plans/active/` before implementation if needed, execute it milestone by milestone with verification and human review, create a git commit after each approved milestone, and move the plan to `docs/exec-plans/completed/` when all milestones are finished.
development1
create-product-specs
Generate or refine repository-local product specification documents for proposed features through interactive discussion with the user. Use when a user describes a feature, workflow, or product behavior they want to build and Codex should ask clarifying questions, define scope, goals, user flows, requirements, and acceptance criteria, then save the result under `docs/product-specs/` such as `docs/product-specs/feature-name.md`. Also use when asked to spec out a feature, write a product spec, turn an idea into a spec, or update an existing product-spec doc.
development1