promote-idea
정보
이 스킬은 IDEAS.md 파일의 앨범 아이디어를 완전한 프로젝트로 자동 변환하며, 기존의 수동 3단계 작업 흐름을 단일 명령어로 대체합니다. 아이디어 제목에서 슬러그를 자동 생성하되 재정의를 허용하며, 다큐멘터리 플래그 옵션도 지원합니다. 사용자가 아이디어를 승격하거나 앨범 컨셉 작업을 시작하도록 요청할 때 개발자가 사용해야 합니다.
빠른 설치
Claude Code
추천npx skills add bitwize-music-studio/claude-ai-music-skills -a claude-code/plugin add https://github.com/bitwize-music-studio/claude-ai-music-skillsgit clone https://github.com/bitwize-music-studio/claude-ai-music-skills.git ~/.claude/skills/promote-ideaClaude Code에서 이 명령을 복사하여 붙여넣어 스킬을 설치하세요
문서
Your Task
Input: $ARGUMENTS
Convert a Pending idea from IDEAS.md into a full album project in one
call. Replaces the manual 3-step workflow (get_ideas → new-album →
update_idea) with a single entry point.
Promote Idea Skill
Step 1: Parse Arguments
Expected formats:
"<idea title>"— auto-derive slug from the title"<idea title>" <album-slug>— override the auto-derived slug"<idea title>" documentary— standard slug, documentary flag on"<idea title>" <album-slug> documentary— explicit slug + documentary
Examples:
"Kleine Welt"→ slug auto-derived tokleine-welt"The Great Molasses Flood" molasses-flood documentary"Ängstliche Kätzchen"→ slugangstliche-katzchen(diacritics stripped)
If no arguments are supplied, or the title is empty, list the available pending ideas first and ask which one to promote:
Which idea should I promote?
Pending ideas:
1. Kleine Welt (electronic, Thematic)
2. The Great Molasses Flood (folk, Documentary)
3. Linux Kernel Wars (electronic, Character Study)
Reply with the exact title.
Use get_ideas(status_filter="Pending") to fetch the list.
Step 2: Confirm the Derived Slug
Call get_ideas(status_filter="Pending") (or search(query=idea_title, scope="ideas"))
to confirm the idea exists and show the user what's about to happen.
Compute the slug locally for display only (lowercase, strip diacritics, non-alphanumeric → hyphen). If the result looks odd, offer to override:
About to promote:
Idea: Kleine Welt
Slug: kleine-welt
Genre: electronic
Type: Thematic
Proceed? (Or supply a different slug.)
Skip the confirmation step if the user has already provided an explicit slug — that's the signal they've already thought about it.
Step 3: Ask About Documentary Flag (if not already supplied)
The documentary flag decides whether RESEARCH.md and SOURCES.md are
created. This is not derivable from idea metadata — the idea's "Type"
field can say "Documentary" but that's a separate concept (narrative shape).
Ask once:
Is this a documentary/true-story album? (Adds research + sources templates. Answer 'yes' for real-world events, 'no' for fiction.)
Skip this step if documentary is already in the arguments.
Step 4: Promote via MCP
Call promote_idea(idea_title, album_slug=<slug or "">, documentary=<bool>).
The tool performs all of:
- Find the idea in state (error if missing or already promoted)
- Create the album directory via
create_album_structure - Inject the idea's concept into the new
README.mdunder a## Conceptsection - Advance idea status
Pending→In Progress - Add
**Promoted To**: <slug>back-link to the idea inIDEAS.md
The tool returns {promoted: true, slug, album_path, files, ...} on
success or {error: ...} on failure.
Step 5: Confirm and Suggest Next Step
On success, report:
Promoted "Kleine Welt" → album "kleine-welt"
Location: ~/bitwize-music/artists/bitwize/albums/electronic/kleine-welt/
Files: README.md, tracks/
Concept block injected into README.md from idea.
Idea status: Pending → In Progress
Next step:
/bitwize-music:album-conceptualizer
This walks through the 7 Planning Phases (Vision, Identity, Sonic
Direction, Structure, Tracks, Content, Approval) to develop the concept
you just carried over into the album.
For documentary albums, add:
Research files also created: RESEARCH.md, SOURCES.md
Don't forget human source verification before generation.
Error Handling
Idea not found:
Error: Idea "Nonexistent" not found in IDEAS.md.
Check available ideas: /bitwize-music:album-ideas list
Idea already promoted:
Error: Idea "Already Active" is already promoted (status: In Progress).
If you want to rename or re-scaffold, use /bitwize-music:rename on the
existing album instead.
Idea has no genre:
Error: Idea "No Genre" has no **Genre** field in IDEAS.md.
Set the genre first: /bitwize-music:album-ideas edit "No Genre"
Invalid genre:
Error: Invalid genre "xyz" on idea. Not in genres/.
Fix the genre in IDEAS.md, then retry.
Duplicate album slug:
Error: Album "kleine-welt" already exists.
Options:
1. Supply a different slug: /bitwize-music:promote-idea "Kleine Welt" kleine-welt-2
2. Resume the existing album: /bitwize-music:resume kleine-welt
Examples
Simple title
/bitwize-music:promote-idea "Kleine Welt"
Auto-derives slug kleine-welt, asks about documentary flag, calls
promote_idea, reports outcome.
Explicit slug override
/bitwize-music:promote-idea "The Great Molasses Flood" molasses-1919
Uses molasses-1919 instead of the auto-derived the-great-molasses-flood.
Documentary album
/bitwize-music:promote-idea "The Great Molasses Flood" documentary
Creates RESEARCH.md and SOURCES.md in addition to the standard README
and tracks directory.
Why a Dedicated Skill
The manual workflow required three steps in sequence:
get_ideasto find the idea's genre/bitwize-music:new-album <slug> <genre>with a slug the user inventedupdate_idea("<title>", "status", "In Progress")
Problems this skill solves:
- Concept transfer — The idea's concept text is now merged into the new album README automatically (manual copy/paste used to be skipped often).
- Status discipline — Ideas no longer linger as
Pendingafter being worked on; the transition is automatic and bidirectional (Promoted Toback-link). - Slug derivation — No more re-inventing the slug; diacritics and punctuation are normalized consistently.
- Single entry point — Newcomers learn one command instead of three.
Remember
- Pending-only — Only
Pendingideas can be promoted.In ProgressandCompleteideas return an error. - One-way operation — Promotion creates files and updates state. There
is no "unpromote"; use
/bitwize-music:renameor manual cleanup if you need to redo. - Concept is preserved — The idea's concept survives in two places
after promotion: the idea's entry in
IDEAS.md(historical record) and the new album'sREADME.md(working document). - Next step is always album-conceptualizer — Promotion only scaffolds; the actual planning happens in the 7 Planning Phases.
GitHub 저장소
연관 스킬
executing-plans
디자인executing-plans 스킬은 검토 체크포인트가 포함된 통제된 배치로 실행할 완전한 구현 계획이 있을 때 사용합니다. 이 스킬은 계획을 불러와 비판적으로 검토한 후, 소규모 배치(기본값 3개 작업)로 작업을 실행하면서 각 배치 사이에 진행 상황을 아키텍트 검토를 위해 보고합니다. 이를 통해 내재된 품질 관리 체크포인트를 갖춘 체계적인 구현이 보장됩니다.
requesting-code-review
디자인이 스킬은 코드 변경 사항을 요구 사항에 따라 분석하기 위해 코드 리뷰어 하위 에이전트를 호출합니다. 작업 완료 후, 주요 기능 구현 후, 또는 메인 브랜치에 병합하기 전에 사용해야 합니다. 이 리뷰는 현재 구현체와 원래 계획을 비교하여 문제를 조기에 발견하는 데 도움이 됩니다.
connect-mcp-server
디자인이 스킬은 개발자들이 HTTP, stdio 또는 SSE 전송 방식을 통해 MCP 서버를 Claude Code에 연결하는 포괄적인 가이드를 제공합니다. GitHub, Notion 및 사용자 정의 API와 같은 외부 서비스를 통합하기 위한 설치, 구성, 인증 및 보안을 다룹니다. MCP 통합 설정, 외부 도구 구성 또는 Claude의 모델 컨텍스트 프로토콜 작업 시 활용하세요.
web-cli-teleport
디자인이 스킬은 작업 분석을 기반으로 개발자가 Claude Code 웹 인터페이스와 CLI 인터페이스 중 선택할 수 있도록 돕고, 두 환경 간 원활한 세션 텔레포트를 가능하게 합니다. 웹, CLI 또는 모바일 환경 전환 시 세션 상태와 컨텍스트를 관리하여 워크플로를 최적화합니다. 다양한 단계에서 서로 다른 도구가 필요한 복잡한 프로젝트에 사용하세요.
