メニュー
Use when a feature is complete or wrapping up implementation in a Rails + React app. Records how the feature was built as a docs file and captures new reusable patterns into each repo's conventions file.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/marvs/kantan-dev --skill kantan-finish-featureコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
SKILL.md を表示中
Use when planning a feature or before writing implementation code in a Rails + React app. Produces an approved implementation plan, asking clarifying questions and grounding the plan in repo conventions and prior feature docs. Never starts implementation.
Use when implementation is complete, before reporting or marking any feature as done, and before finishing a feature in a Rails + React app. Mandatory review step of the Kantan workflow — never skip it. Performs an expert Rails + React code review of the changes against the plan, the repo conventions, and universal best practices.
Use when implementing Rails backend code — models, services, controllers, jobs, or APIs. Follows the backend repo's own conventions, applies test-driven development, and keeps the test suite and linter green.
| name | kantan-finish-feature |
| description | Use when a feature is complete or wrapping up implementation in a Rails + React app. Records how the feature was built as a docs file and captures new reusable patterns into each repo's conventions file. |
Run this after kantan-review-feature has passed (no Critical or Major findings remaining) and tests and linters are green on both stacks.
Before anything else, read <backend-root>/.kantan-dev/reviews/YYYYMMDD_feature_name.md (same slug as the idea/plan).
kantan-review-feature first, then return here.Verdict: APPROVED, STOP — blocking findings remain. Resolve them via the review loop first.APPROVED.Write every document and chat message from this skill in ASD-STE100 Simplified Technical English — a restricted form of English built for technical documents that a non-native reader must get right on one reading. Later agent sessions read these files too.
endpoint stays "endpoint", never "route" or "API surface".Create <backend-root>/.kantan-dev/docs/YYYYMMDD_feature_name.md (same slug as the idea/plan). One consolidated doc covering backend and frontend. Include:
Purpose: future agent sessions read these for context. Be concrete.
Review the changes for anything generic and reusable (not feature-specific): new service/controller/model patterns, testing helpers, component/API/state patterns, library integrations, migration conventions.
For each reusable pattern, update the relevant repo's conventions file — write to AGENTS.md if it exists, otherwise CLAUDE.md. Backend patterns go in the backend's file; frontend patterns go in that frontend's file. Keep entries concise and prescriptive (tell future agents what to do, not what was done).
Do NOT run git add or git commit. Leave all changes — code, docs, and conventions updates — for the user to review and push.