agile-proces
This skill guides agents and developers through the Kanban workflow defined in `orgs/riatzukiza/promethean/docs/agile/process.md`.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
メニュー
This skill guides agents and developers through the Kanban workflow defined in `orgs/riatzukiza/promethean/docs/agile/process.md`.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Protocol to stop apology loops and focus on verified fixes.
Protocol to break out of repetitive, failing edit loops by forcing analysis over action.
Resolves Clojure namespace-path mismatches and classpath errors with definitive path conversion
Auto-fix Clojure delimiters and validate syntax with OpenCode tools.
Protocol to recover from Clojure/Script syntax errors, specifically bracket mismatches and EOF errors.
Create new pm2-clj ecosystem configuration files from scratch or templates for PM2 process management
| name | agile-proces |
| description | This skill guides agents and developers through the Kanban workflow defined in `orgs/riatzukiza/promethean/docs/agile/process.md`. |
This skill guides agents and developers through the Kanban workflow defined in orgs/riatzukiza/promethean/docs/agile/process.md.
The board functions as a Finite State Machine (FSM). Tasks/Specs must exist in exactly one state.
icebox)status: iceboxbacklog)status: backlogtodo)status: todoin-progress)status: in-progressreview)status: reviewdocument)status: documentdone)status: doneWhen moving a task:
status field in the front matter.updated_at.Dispatch sub agents to investigate the current status of each issue in the projects github mapping each to an existing repo/project spec if possible. Add A comment to each issue communicating what you believe it's current state to be. Then add a label to that issue corresponding to a state in @docs/reference/process.md create new work trees for each confirmed issue that is ready to work on and dispatch an agent to work on that issue. For each issue confirmed to be valid, but requires triage, dispatch an agent to clarify the issue and associated spec. For each @gates-pr35-hardening-main/spec/ that does not have a corresponding issue, create an issue and give it an appropriate label. If the github label to match a current status that is a valid state in the process FSM, create that label.