From nightshift
Creates a new Nightshift shift directory with manager.md and empty table.csv for structured batch agent work. Required before using other Nightshift commands.
How this skill is triggered — by the user, by Claude, or both
Slash command
/nightshift:createThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Create a new Nightshift shift named `$ARGUMENTS`.
Create a new Nightshift shift named $ARGUMENTS.
Steps
Resolve the shift name
$ARGUMENTS is non-empty, treat it as the shift name.$ARGUMENTS is empty, use the AskUserQuestion tool (open-ended) to ask:
"What will this shift do? Describe the batch work and I'll derive a name."
create-promo-examples).Validate the name
Check for conflicts
.nightshift/<name>/ already exists, report: "Shift <name> already exists. Use /nightshift:start <name> to resume it."Run the bundled init script
${CLAUDE_SKILL_DIR}/scripts/init-shift.sh <name>
The script does two things, both idempotent:
.nightshift/archive/ exists and creates .nightshift/.gitignore with default ignore patterns if absent. This replaces the work nightshift init used to do at install time — a fresh project never needs a separate "init" step..nightshift/<name>/ containing manager.md with default Shift Configuration and an empty Task Order, plus table.csv empty (no header row — columns are added when tasks are defined).Ask about initial tasks
Use the AskUserQuestion tool to ask:
"Shift
<name>created! Do you want to add a task now?"
Options: "Yes, add a task" / "No, I'll add tasks later"
If yes, guide them through the /nightshift:add-task <name> flow.
Output
## Shift Created: <name>
**Location:** `.nightshift/<name>/`
**Files:** manager.md, table.csv
### Next Steps
- `/nightshift:add-task <name>` — add tasks to the shift
- `/nightshift:update-table <name>` — add items to the table
- `/nightshift:start <name>` — begin execution (after adding tasks and items)
### Environment Variables (Optional)
Create `.nightshift/<name>/.env` to define environment variables for this shift.
Use `{ENV:VAR_NAME}` in task steps to reference them. The `.env` file is gitignored.
Available template variables in task steps:
- `{column_name}` — table item column value
- `{ENV:VAR_NAME}` — environment variable from `.env`
- `{SHIFT:FOLDER}` — shift directory path
- `{SHIFT:NAME}` — shift name
- `{SHIFT:TABLE}` — full path to table.csv
Guardrails
created field — the script handles this.npx claudepluginhub johndaskovsky/nightshift --plugin nightshiftAdds a task definition to an existing Nightshift shift, registering it in manager.md and adding a status column to table.csv. Invoked via /nightshift:add-task.
Interactively designs plain-text workflows with stages, entities, and a first-officer agent, then generates markdown files and launches a pilot run.
Authors a reusable, deterministic agent orchestration workflow as a self-contained .mjs script for Claude Code's Workflow tool, with structured phases, fan-out, and verification.