series-create
Skill16 starsChanged 2 days agoApache-2.0View on GitHub
Create a validated sequential Issue series plan from an explicitly ordered GitHub Issue list. Use when a maintainer wants to generate or update an ID-named YAML file under .kaji/series, select standard workflows from Issue type metadata and workflow descriptions, or preview a series without starting it.
In this repository46 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- llms.txtllms.txt
- baseline-precheckSkill
- grill-meSkill
- herdr-kaji-launchSkill
- i-dev-final-checkSkill
- i-doc-final-checkSkill
- i-doc-fixSkill
- i-doc-reviewSkill
- i-doc-updateSkill
- i-doc-verifySkill
- incident-cycleSkill
- incident-fixSkill
- incident-investigateSkill
- incident-reportSkill
- incident-reviewSkill
- incident-verifySkill
- i-prSkill
- issue-closeSkill
- issue-createSkill
- issue-designSkill
- issue-fix-codeSkill
- issue-fix-designSkill
- issue-fix-readySkill
- issue-implementSkill
- issue-review-codeSkill
- issue-review-designSkill
- issue-review-readySkill
- issue-small-change-executeSkill
- issue-small-change-reviewSkill
- issue-startSkill
- issue-verify-codeSkill
- issue-verify-designSkill
- kaji-run-verifySkill
- pr-fixSkill
- pr-verifySkill
- releaseSkill
- release-starterSkill
- review-cycleSkill
- review-pollSkill
- reviewSkill
- review-starter-updateSkill
- run-watchedSkill
- update-starterSkill
- watch-triageSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 3 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 25
Read each Issue without mutation:
- Very specific: line 31
Read every .kaji/wf/official//*.yaml and .kaji/wf/custom//*.yaml description and requires_provider value.
- Very specific: line 46
If the target exists without --update, stop.
- Distinctive: line 47
Run both checks and stop if either fails:
- Distinctive: line 62
No Issue, PR, label, sub-issue, state, lock, or member-run mutation.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Series Create
Generate a deterministic series YAML, validate it, show its dry-run plan, and stop before execution.
Input
Accept this manual form:
/series-create <issue>... --id <series-id> [--parent <issue>]
[--workflow <issue>=<repo-relative-path>]... [--update]Preserve Issue order exactly. Treat --workflow as a member-specific override. Require --id and at
least one positive integer Issue number.
Workflow
- Confirm
kaji config provider-typereturnsgithub; otherwise stop. Read each Issue without mutation:
kaji issue view <issue> --json labels,title,state- Read every
.kaji/wf/official/**/*.yamland.kaji/wf/custom/**/*.yamldescriptionandrequires_providervalue. For each member without an override, select candidates whose description says they are the standard series auto-selection target for the Issue's singletype:label and whose provider isgithuborany. - Auto-select only when exactly one candidate remains. Display the Issue type and matching
description sentence as the reason. If the Issue has zero or multiple
type:labels, or the candidate count is not one, stop and request--workflow <issue>=<path>for that member. Invoke the deterministic generator. Do not write YAML manually:
python -m kaji_harness.scripts.series_generate \ --id <series-id> [--parent <parent>] \ --member <issue>=<workflow>... \ --output .kaji/series/<series-id>.yaml [--update]- If the target exists without
--update, stop. Never retry with--updateimplicitly. Run both checks and stop if either fails:
kaji validate-series .kaji/series/<series-id>.yaml kaji run-series .kaji/series/<series-id>.yaml --dry-run- Report the generated path, ordered members, workflow selection reasons, validation result, and
dry-run plan. Do not start
kaji run-serieswithout--dry-run.
Output
- One
.kaji/series/<id>.yamlcontaining onlyid, optionalparent_issue,strategy, orderedmemberswith resolved workflow paths, andon_failure. - A console summary of selection reasons and the validated dry-run plan.
- No Issue, PR, label, sub-issue, state, lock, or member-run mutation.
Stop Conditions
- Provider is not GitHub.
- Input is malformed or Issue type metadata is missing/ambiguous.
- Workflow selection is not unique and no override was supplied.
- An override path fails
validate-series. - The output exists without explicit
--update. - Generation, validation, or dry-run returns nonzero.
Non-goals
- Discovering members from an EPIC, parent body, or sub-issue relation.
- Reordering members or inferring dependencies.
- Editing Issue metadata or external state.
- Duplicating schema validation or YAML serialization in the agent.
- Starting the actual series execution.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

