feat: Claude Code Routines パイプライン prompt 6種を追加#124
Open
TakuTsuchida wants to merge 7 commits into
Open
Conversation
Cloud Routine source for claude.ai/code/routines: the PO persona turns the oldest `requirement` issue into a `user-story` issue so the autonomous pipeline has a value-framed, acceptance-criteria-backed starting point. Co-Authored-By: Claude <noreply@anthropic.com>
Cloud Routine source: an architect persona converts the oldest `user-story` issue into a `design` issue. Centralizing extensibility decisions here keeps downstream implementation issues small and consistent with existing patterns. Co-Authored-By: Claude <noreply@anthropic.com>
Cloud Routine source: splitting the `design` issue into <=200-line `implement` sub-issues is what keeps each implementation run cheap enough for Sonnet and each PR small enough to review autonomously. Co-Authored-By: Claude <noreply@anthropic.com>
Cloud Routine source adapted from the launchd 01.Implementation prompt, but self-contained and pinned to Sonnet per the pipeline cost model, and unified on the `implement` label so it chains cleanly after design decomposition. Co-Authored-By: Claude <noreply@anthropic.com>
Cloud Routine source adapted from the launchd 02.pr-review prompt, pinned to Sonnet and made self-contained. Gating merge on green CI is what lets the review stage run unattended without lowering the quality bar. Co-Authored-By: Claude <noreply@anthropic.com>
Cloud Routine source: a weekly tech-lead sweep scoped by perspective (frontend / backend / contract / screens / reuse) rather than crawling all code, emitting `implement`-labeled fixes so quality work re-enters the same implement->PR->merge loop. Co-Authored-By: Claude <noreply@anthropic.com>
…ing it Routines are UI-registered, not file-loaded, so the source files alone leave the Model/Schedule/Repository/Trigger settings implicit. This index makes the registration steps and the per-run quota caps explicit for whoever sets them up. Co-Authored-By: Claude <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
背景 / 課題
TakuTsuchida/claude-code-scheduler#10のコメントで設計された、technical-fundamental-backtester向けラベル駆動の自律開発パイプライン（requirement → user-story → design → implement → PR → review/merge）を、コスト面（ECS + Anthropic API はサブスク枠と別課金）からクラウドの Claude Code Routines（サブスク枠で実行）として運用したい。これまで上流（要件定義・設計）と品質（バグ調査）の routine prompt が存在せず、パイプラインが下流（実装・レビュー）の launchd 方式しか揃っていなかった。
目的・スコープ
目的: クラウド Routines に登録する 6 種の prompt を、版管理可能な登録用ソースとして整備する。
対象外:
.claude/scripts/routine-engineering.sh、01.Implementation.md/02.pr-review.md）の変更変更概要
.claude/scripts/prompts/routines/を新設し、issue 記載の全タスクを 1 ファイル 1 routine で作成（各ファイル先頭に Model / Schedule / Trigger / GitHub Repository を記載）:01.create-user-story.md（PO / Opus /requirement→user-story）02.design-from-user-story.md（architect / Opus /user-story→design）03.decompose-design-to-issues.md（architect / Opus /design→implementsub-issue 複数・各200行以内）04.implement-and-create-pr.md（engineer / Sonnet /implement→PR）05.pr-review-and-merge.md（tech-lead / Sonnet / open PR→レビュー→squash merge）06.investigate-bugs-create-issues.md（tech-lead / Opus / コードベース→implementfix issue 複数）README.md（登録手順 + ルーチン一覧 + 実行上限の留意点）期待される効果
品質チェック
requirement/user-story/design/implementに統一、各 prompt は自己完結レビュー観点
routines:名前空間ではなく issue 準拠の素ラベルに統一した点参照: TakuTsuchida/claude-code-scheduler#10