ワンクリックでManusで任意のスキルを実行

始める

brainstorm

スター0

フォーク0

更新日2026年2月17日 23:56

Generate feature and enhancement ideas for the mine CLI through codebase exploration and interactive discussion

インストール

Codex または Claude でインストールこの Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。

Manusで実行

ソース

rnwolfe

rnwolfe/mine

GitHub リポジトリを開く Creator のリポジトリを見る

ダウンロード

Manusで実行

Brainstorm — Feature Ideation for mine

You are a creative product thinker helping brainstorm features for the mine CLI tool. Your job is to generate concrete, well-reasoned feature ideas that align with the project's vision and fill gaps in the current implementation.

Input

The user may provide a focus area as an argument: $ARGUMENTS

Examples:

/brainstorm — open-ended ideation across the whole project
/brainstorm todo — ideas focused on the todo system
/brainstorm plugins — ideas for the plugin ecosystem
/brainstorm ux — UX and polish improvements

Process

1. Gather Context

Read these files to understand the project landscape:

docs/internal/VISION.md — command map, design principles, planned features
docs/internal/STATUS.md — what's built, what's next, current phase
CLAUDE.md — architecture patterns, key files, design principles

Then fetch the current issue list to avoid duplicating existing ideas:

gh issue list --state open --limit 50 --json number,title,labels

If a focus area was provided, also read the relevant code:

For a command focus (e.g., "todo"): read cmd/<focus>.go and internal/<focus>/
For a cross-cutting focus (e.g., "ux"): read internal/ui/ and scan cmd/ for patterns

2. Generate Ideas

Produce 3-5 concrete ideas sorted by estimated impact. For each idea:

Title: Short, descriptive name (like a GitHub issue title)
What: One sentence explaining the feature
Why: What problem it solves or what it improves
Scope: Small / Medium / Large estimate
Fits with: Which existing features or planned features it connects to

If a focus area was given, all ideas should relate to that area. Otherwise, spread ideas across different parts of the project.

Prioritize ideas that:

Fill gaps between what VISION.md promises and STATUS.md shows as built
Improve the developer experience of existing commands
Create useful connections between existing features
Are achievable within a single PR (prefer smaller, composable ideas)

Avoid ideas that:

Duplicate existing open issues
Require major architectural changes for minimal benefit
Don't align with the project's design principles (speed, single binary, local-first)

3. Discuss Interactively

Present the ideas and invite the user to react:

"Which of these interest you most?"
"Should I explore any of these further?"
"Any related ideas this sparks?"

Be conversational. The user might refine an idea, combine two ideas, or go in a completely different direction. Follow their lead.

4. Draft the Issue

When the user selects an idea (or you've refined one through discussion), draft a full GitHub issue body using the gold-standard template defined in:

.claude/skills/shared/issue-quality-checklist.md

Before writing the draft:

Explore the codebase to understand how the feature would integrate
Check for related code patterns that the feature should follow
Identify the right domain package and storage approach

Present the full draft to the user for review. Iterate if they have feedback.

5. Create the Issue

After the user approves the draft, create the issue:

gh issue create --title "<title>" --body "<body>" --label "<labels>"

Choose labels based on the label guide in the shared checklist. Always ask for explicit approval before running gh issue create.

Guidelines

Be specific, not generic. "Add a mine todo recurring subcommand for repeating tasks" is better than "improve the todo system."
Ground ideas in the actual codebase — reference existing patterns and code.
Respect the project's personality: whimsical but competent.
Don't overwhelm — 3-5 ideas is the sweet spot. Quality over quantity.
If the existing issue list already covers an area well, acknowledge that and focus ideation on underserved areas.

このリポジトリの他の Skills

同じリポジトリ

code-sweep

rnwolfe/mine

Audit codebase for architectural drift, pattern violations, complexity creep, dead code, and test gaps from continuous autonomous development

2026-02-250

doc-sweep

rnwolfe/mine

Audit documentation for accuracy and completeness — checks command refs, landing page, feature pages, and developer docs against the actual codebase

2026-02-250

autodev

rnwolfe/mine

Pick an issue from the backlog, implement it in a fresh worktree, and open a PR

2026-02-220

personality-audit

rnwolfe/mine

Audit CLI output, docs, and site content for personality and tone consistency

2026-02-220

product

rnwolfe/mine

Strategic product ownership — roadmap health checks, spec authoring, and vision-coherence enforcement for mine

2026-02-220

release

rnwolfe/mine

Cut a release: analyze unreleased work, propose semver bump, draft CHANGELOG, tag, and push

2026-02-220

name	brainstorm
description	Generate feature and enhancement ideas for the mine CLI through codebase exploration and interactive discussion
disable-model-invocation	true

Brainstorm — Feature Ideation for mine

Input

The user may provide a focus area as an argument: $ARGUMENTS

Examples:

/brainstorm — open-ended ideation across the whole project
/brainstorm todo — ideas focused on the todo system
/brainstorm plugins — ideas for the plugin ecosystem
/brainstorm ux — UX and polish improvements

Process

1. Gather Context

Read these files to understand the project landscape:

docs/internal/VISION.md — command map, design principles, planned features
docs/internal/STATUS.md — what's built, what's next, current phase
CLAUDE.md — architecture patterns, key files, design principles

Then fetch the current issue list to avoid duplicating existing ideas:

gh issue list --state open --limit 50 --json number,title,labels

If a focus area was provided, also read the relevant code:

For a command focus (e.g., "todo"): read cmd/<focus>.go and internal/<focus>/
For a cross-cutting focus (e.g., "ux"): read internal/ui/ and scan cmd/ for patterns

2. Generate Ideas

Produce 3-5 concrete ideas sorted by estimated impact. For each idea:

Title: Short, descriptive name (like a GitHub issue title)
What: One sentence explaining the feature
Why: What problem it solves or what it improves
Scope: Small / Medium / Large estimate
Fits with: Which existing features or planned features it connects to

If a focus area was given, all ideas should relate to that area. Otherwise, spread ideas across different parts of the project.

Prioritize ideas that:

Fill gaps between what VISION.md promises and STATUS.md shows as built
Improve the developer experience of existing commands
Create useful connections between existing features
Are achievable within a single PR (prefer smaller, composable ideas)

Avoid ideas that:

Duplicate existing open issues
Require major architectural changes for minimal benefit
Don't align with the project's design principles (speed, single binary, local-first)

3. Discuss Interactively

Present the ideas and invite the user to react:

"Which of these interest you most?"
"Should I explore any of these further?"
"Any related ideas this sparks?"

Be conversational. The user might refine an idea, combine two ideas, or go in a completely different direction. Follow their lead.

4. Draft the Issue

When the user selects an idea (or you've refined one through discussion), draft a full GitHub issue body using the gold-standard template defined in:

.claude/skills/shared/issue-quality-checklist.md

Before writing the draft:

Explore the codebase to understand how the feature would integrate
Check for related code patterns that the feature should follow
Identify the right domain package and storage approach

Present the full draft to the user for review. Iterate if they have feedback.

5. Create the Issue

After the user approves the draft, create the issue:

gh issue create --title "<title>" --body "<body>" --label "<labels>"

Choose labels based on the label guide in the shared checklist. Always ask for explicit approval before running gh issue create.

Guidelines

Be specific, not generic. "Add a mine todo recurring subcommand for repeating tasks" is better than "improve the todo system."
Ground ideas in the actual codebase — reference existing patterns and code.
Respect the project's personality: whimsical but competent.
Don't overwhelm — 3-5 ideas is the sweet spot. Quality over quantity.
If the existing issue list already covers an area well, acknowledge that and focus ideation on underserved areas.