Shopl Sprint Planner

Install the shopl-sprint-planner Codex skill from npm and load it into your local Codex skills directory.

What It Installs

• SKILL.md
• agents/openai.yaml

The installer copies both files into:

• $CODEX_HOME/skills/shopl-sprint-planner, or
• ~/.codex/skills/shopl-sprint-planner when CODEX_HOME is not set

Requirements

• Node.js 18+
• npm
• Codex with local skill loading enabled

Quick Start

Run the installer directly from npm:

npx @gyub.s/codex-skill-shopl-sprint-planner

Then start a new Codex session. The skill will be available as shopl-sprint-planner.

Global Install

If you want a reusable local command:

npm install -g @gyub.s/codex-skill-shopl-sprint-planner
shopl-sprint-planner

The legacy alias also works:

shopl-sprint-planner-skill

Custom Target Directory

Install into a custom skills directory:

npx @gyub.s/codex-skill-shopl-sprint-planner -- --target /path/to/skills

Preview the install without writing files:

npx @gyub.s/codex-skill-shopl-sprint-planner -- --dry-run

Verify Installation

Check that the files were copied:

ls ~/.codex/skills/shopl-sprint-planner

Expected files:

• SKILL.md
• agents/openai.yaml

Usage

In a new Codex session, invoke the skill with a prompt such as:

Use $shopl-sprint-planner to interview me, split a Shopl upper Jira ticket, create real child tickets first when needed, and write docs/work-plans.

Publish To npm

If you are publishing this package for the first time:

npm login
npm run release:check
npm publish

Or publish through GitHub Actions:

1. Add NPM_TOKEN to the repository secrets.
2. Push a tag such as v0.1.0.
3. The workflow at .github/workflows/publish.yml will validate and publish the package.

Continuous Publish Without Web

You can set up repeatable npm publishing without opening the npm or GitHub web UI each time.

1. Create a publish token from the CLI

Create a write token that can bypass 2FA for publish automation:

npx [email protected] token create \
  --name "shopl-sprint-planner-publish" \
  --token-description "shopl-sprint-planner publish" \
  --scopes gyub.s \
  --packages-and-scopes-permission read-write \
  --bypass-2fa=true

If your locally installed npm already supports granular token creation, this also works:

npm token create \
  --name "shopl-sprint-planner-publish" \
  --token-description "shopl-sprint-planner publish" \
  --scopes gyub.s \
  --packages-and-scopes-permission read-write \
  --bypass-2fa=true

Notes:

• npm may prompt for your password and one-time password during token creation.
• This is a one-time setup step for generating the token.
• npm's latest CLI docs describe npm token create support for granular tokens and bypass-2fa.
• On the machine used for this repository, npm 11.6.2 did not recognize the granular token flags, so npx [email protected] ... is the safer command.

2. Export the token in your shell

export NPM_TOKEN="paste-the-token-here"

3. Persist it locally and in GitHub Actions

This command writes the token to ~/.npmrc and, if gh is authenticated, sets the repository secret NPM_TOKEN without opening GitHub in a browser:

npm run setup:publish-token -- --gh-secret

Dry-run:

npm run setup:publish-token -- --gh-secret --dry-run

4. Publish continuously

Local publish with the stored token:

npm publish

GitHub Actions publish by tag:

git tag v0.1.0
git push origin v0.1.0

The workflow at .github/workflows/publish.yml uses the NPM_TOKEN secret for non-interactive publishing.

Notes:

• The current package name is @gyub.s/codex-skill-shopl-sprint-planner.
• The @gyub.s npm user scope belongs to the gyub.s npm account.
• publishConfig.access is set to public. If you want a private org package instead, change it back to restricted before publishing.
• The package is currently marked UNLICENSED. If this will be distributed outside your company, choose an explicit license first.