Run any Skill in Manus with one click

mm-feature-rnd

Stars6

Forks0

UpdatedJune 9, 2026 at 23:24

Feature R&D via a dynamic workflow. Mine a codebase's roadmap, scaffolded/gated features, ADRs, and novel ideas for net-new feature candidates; generate full design specs; score them with a judge panel on value/effort/risk/differentiation; synthesize a ranked HTML feature catalog. Use when the user asks "what should we build next", "feature ideas", "R&D", "find net-new features", or wants a decision-ready catalog of buildable features (not bug fixes). Read-only — produces designs + a catalog, writes no feature code.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

wolverin0

wolverin0/memorymaster

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

File Explorer

2 files

SKILL.md

readonly

name	mm-feature-rnd
description	Feature R&D via a dynamic workflow. Mine a codebase's roadmap, scaffolded/gated features, ADRs, and novel ideas for net-new feature candidates; generate full design specs; score them with a judge panel on value/effort/risk/differentiation; synthesize a ranked HTML feature catalog. Use when the user asks "what should we build next", "feature ideas", "R&D", "find net-new features", or wants a decision-ready catalog of buildable features (not bug fixes). Read-only — produces designs + a catalog, writes no feature code.
version	1.0.0

mm-feature-rnd — Feature R&D Catalog (dynamic workflow embedded in a skill)

Runs a multi-agent dynamic workflow that discovers net-new feature candidates from real project evidence, designs each one, scores them with a judge panel, and renders a ranked HTML catalog you pick from. This is the harness that produced a 17-feature scored catalog for MemoryMaster (2026-06-01).

When to use

"what should we build next", "feature ideas", "R&D session", "roadmap mining"
You want grounded, buildable feature proposals (scored, with full specs) — NOT generic brainstorming, NOT bug fixes/refactors (those are out of scope).

How it works (phases)

Scout — parallel agents mine: roadmap/backlog files, scaffolded/env-gated half-built features, ADRs/architecture for under-exploited primitives, and novel differentiators vs competitors. Curate to a deduped slate.
Design — one full design spec per candidate (problem, design on the real stack, surface, effort S/M/L/XL, risk, differentiation, test plan, deps).
Judge — 2 judges per design (product-value + build-pragmatics lenses) score value/effort/risk/differentiation; deterministic in-code tally.
Synthesize — executive "build-first" list + themes.

Run it

Confirm scope — the repo + that this is features/improvements only (no bugs/cleanup). The embedded SCOUT_SLICES/CONTEXT/GROUPS are MemoryMaster-tuned; for another project edit the copy first.
Launch:
```
Workflow({ scriptPath: ".claude/skills/mm-feature-rnd/feature-catalog.workflow.js" })
```
Returns { stats, synthesis{executive_summary, build_first[], themes[]}, catalog[] }.
Render the HTML catalog from the .output file via a small Python script (severity/score-ranked cards, filterable by verdict) to C:\Users\pauol\artifacts\YYYY-MM-DD-<slug>.html, then open it. Don't pull the full result into context.
Present the top "build-first" features inline; let the USER pick which to prototype. Prototyping is a SEPARATE gated step (worktree builds + tests) — never auto-build features.

Adapting to another repo

Edit REPO, CONTEXT (project + competitors), and SCOUT_SLICES (which files to mine) at the top of the workflow .js. Keep the judge-panel + tally intact.

Guardrails

Read-only / design-only. Produces specs + a catalog; writes no feature code.
Features only. Drop anything that is a bug fix, test, refactor, or cleanup.
Trust scores, not verdict prose. The 2-judge median can skew labels pessimistic; rank by the numeric score + the synthesis build-first list.
Verify "already exists" claims before building later. Scout/design agents hallucinate both directions about what's already built — any follow-up build MUST grep/read the real code first (see ref mm-712f).

More from this repository

same repository

gitnexus-cli

wolverin0/memorymaster

Use when the user needs to run GitNexus CLI commands like analyze/index a repo, check status, clean the index, generate a wiki, or list indexed repos. Examples: "Index this repo", "Reanalyze the codebase", "Generate a wiki"

2026-06-306

mm-audit

wolverin0/memorymaster

Deep adversarial code audit via a dynamic workflow. Fan-out finders across correctness/concurrency/security/perf/contract dimensions × module groups, dedup, then 3-skeptic adversarial refute-verify, completeness critic, and a ranked HTML findings report. Use when the user asks for a "deep audit", "adversarial audit", "find all the bugs", "security+correctness sweep", or wants an exhaustive review that goes beyond a single-context pass. Read-only — produces a report, does not change code.

2026-06-096

mm-mine-corrections

wolverin0/memorymaster

Mine your own correction history for recurring rules. A dynamic workflow harvests user-correction turns from the MemoryMaster verbatim corpus (857k+ rows), distills each to a prescriptive rule, clusters recurring themes, and proposes evidence-linked SKILLS / rule-claims (not CLAUDE.md bloat) — each backed by the source verbatim ids. Use when the user asks to "mine my corrections", "find the rules I keep repeating", "what do I keep telling Claude not to do", "turn my sessions into skills", or wants to harden behavior from real feedback. Read-only on the DB — proposes, does not auto-write rules.

2026-06-096

name	mm-feature-rnd
description	Feature R&D via a dynamic workflow. Mine a codebase's roadmap, scaffolded/gated features, ADRs, and novel ideas for net-new feature candidates; generate full design specs; score them with a judge panel on value/effort/risk/differentiation; synthesize a ranked HTML feature catalog. Use when the user asks "what should we build next", "feature ideas", "R&D", "find net-new features", or wants a decision-ready catalog of buildable features (not bug fixes). Read-only — produces designs + a catalog, writes no feature code.
version	1.0.0

mm-feature-rnd — Feature R&D Catalog (dynamic workflow embedded in a skill)

When to use

"what should we build next", "feature ideas", "R&D session", "roadmap mining"
You want grounded, buildable feature proposals (scored, with full specs) — NOT generic brainstorming, NOT bug fixes/refactors (those are out of scope).

How it works (phases)

Scout — parallel agents mine: roadmap/backlog files, scaffolded/env-gated half-built features, ADRs/architecture for under-exploited primitives, and novel differentiators vs competitors. Curate to a deduped slate.
Design — one full design spec per candidate (problem, design on the real stack, surface, effort S/M/L/XL, risk, differentiation, test plan, deps).
Judge — 2 judges per design (product-value + build-pragmatics lenses) score value/effort/risk/differentiation; deterministic in-code tally.
Synthesize — executive "build-first" list + themes.

Run it

Confirm scope — the repo + that this is features/improvements only (no bugs/cleanup). The embedded SCOUT_SLICES/CONTEXT/GROUPS are MemoryMaster-tuned; for another project edit the copy first.
Launch:
```
Workflow({ scriptPath: ".claude/skills/mm-feature-rnd/feature-catalog.workflow.js" })
```
Returns { stats, synthesis{executive_summary, build_first[], themes[]}, catalog[] }.
Render the HTML catalog from the .output file via a small Python script (severity/score-ranked cards, filterable by verdict) to C:\Users\pauol\artifacts\YYYY-MM-DD-<slug>.html, then open it. Don't pull the full result into context.
Present the top "build-first" features inline; let the USER pick which to prototype. Prototyping is a SEPARATE gated step (worktree builds + tests) — never auto-build features.

Adapting to another repo

Edit REPO, CONTEXT (project + competitors), and SCOUT_SLICES (which files to mine) at the top of the workflow .js. Keep the judge-panel + tally intact.

Guardrails

Read-only / design-only. Produces specs + a catalog; writes no feature code.
Features only. Drop anything that is a bug fix, test, refactor, or cleanup.
Trust scores, not verdict prose. The 2-judge median can skew labels pessimistic; rank by the numeric score + the synthesis build-first list.
Verify "already exists" claims before building later. Scout/design agents hallucinate both directions about what's already built — any follow-up build MUST grep/read the real code first (see ref mm-712f).