agileflow 4.0.0-alpha.2 → 4.0.0-alpha.21

package/content/plugins/ideation/skills/agileflow-ideation/workflows/features.md

@@ -0,0 +1,65 @@
+# Features Workflow — Multi-Agent Feature Brainstorm Audit
+
+**Triggers:** "find missing features", "feature brainstorm audit", "what features should we add", "analyze the app for feature gaps", "UX audit for features", "what are we missing compared to competitors"
+
+**Goal:** Deploy multiple specialized brainstorm analyzers in parallel against the codebase or a specific directory, deduplicate and prioritize their findings through a consensus pass, and produce a Feature Brainstorm Report with HIGH_VALUE / MEDIUM_VALUE / NICE_TO_HAVE / SPECULATIVE ratings.
+
+## Inputs needed
+
+| Input       | Required | How to get it                                                      |
+| ----------- | -------- | ------------------------------------------------------------------ |
+| target path | No       | Default: `.` (whole project). Can be a file or directory           |
+| depth       | No       | Default: quick (3 core analyzers). Options: deep (all 5 analyzers) |
+| focus       | No       | Default: all. Options: features, ux, market, growth, integration   |
+
+## Steps
+
+1. Ask the user: "What should I analyze?" Options: [A] The whole project (recommended), [B] A specific directory (e.g., `app/`, `src/`), [C] A specific file.
+
+2. Ask: "Depth?" Options: [A] Quick — 3 core analyzers, fast results (recommended for first pass), [B] Deep — all 5 analyzers, comprehensive coverage.
+
+3. Ask: "Focus area?" Options: [A] All areas, [B] Feature gaps only, [C] UX improvements, [D] Market-standard patterns, [E] Growth opportunities, [F] Integration gaps.
+
+4. Read the target path to understand what the application currently does.
+
+5. Deploy analyzers simultaneously based on depth/focus selection:
+   - **Features analyzer** — what features are absent that similar apps have
+   - **UX analyzer** — friction points, missing affordances, incomplete flows
+   - **Market analyzer** — market-standard patterns and competitive gaps (deep only)
+   - **Growth analyzer** — viral loops, retention mechanics, power user features (deep only)
+   - **Integration analyzer** — third-party services that would add obvious value (deep only)
+
+6. Collect all outputs. Run consensus coordination: deduplicate suggestions that multiple analyzers identified, vote on priority, assign value ratings:
+   - **HIGH_VALUE**: 2+ analyzers identified it, clear user benefit, feasible
+   - **MEDIUM_VALUE**: 1 analyzer with strong evidence or 2 with weaker evidence
+   - **NICE_TO_HAVE**: low complexity, minor improvement
+   - **SPECULATIVE**: interesting but needs validation
+
+7. Present the Feature Brainstorm Report:
+   - HIGH_VALUE features with implementation complexity estimate
+   - MEDIUM_VALUE features grouped by theme
+   - NICE_TO_HAVE quick wins
+   - Summary: N total ideas, X high-value, Y medium-value
+
+8. Ask the user: [A] Create an Epic for the top HIGH_VALUE feature, [B] Generate product briefs for multiple features, [C] Save the report, [D] Narrow to a specific category.
+
+## Output
+
+Feature Brainstorm Report with prioritized, deduplicated suggestions. Value ratings (HIGH_VALUE / MEDIUM_VALUE / NICE_TO_HAVE / SPECULATIVE). Implementation complexity estimates. Optional Epic or product brief for selected features.
+
+## Fallbacks
+
+**If interactive prompts (AskUserQuestion) are unavailable:**
+Present options as a numbered list in your response. Ask the user to reply with a number. Example:
+
+```
+How would you like to proceed?
+1. Fix the P0 findings now
+2. Review full findings first
+3. Export report only
+```
+
+**If agent spawning (Task tool / multi-agent) is unavailable:**
+Perform each analysis inline and sequentially instead of spawning parallel agents.
+Work through the key checks for each domain yourself using the reference files in `references/`.
+Consolidate findings into the same structured output format — the user gets the same result, just slower.

package/content/plugins/ideation/skills/agileflow-ideation/workflows/ideate.md

@@ -0,0 +1,54 @@
+# Ideate Workflow — Feature Discovery and Ideation Session
+
+**Triggers:** "run ideation", "brainstorm features", "discover new ideas", "ideation session", "what could we build next", "feature discovery for [topic]"
+
+**Goal:** Run a structured discovery session — brainstorm new feature ideas, optionally research them, and generate a product brief — all tracked in the ideation history.
+
+## Inputs needed
+
+| Input | Required | How to get it                                             |
+| ----- | -------- | --------------------------------------------------------- |
+| topic | No       | Ask: "What area should we ideate around?"                 |
+| scope | No       | Default: all. Options: all, specific area, single feature |
+
+## Steps
+
+1. Ask the user: "What area should we ideate around?" Options: [A] The whole product (discover broad opportunities), [B] A specific feature area (user onboarding, checkout, settings, etc.), [C] A specific user problem I have in mind.
+
+2. Read the project structure to understand what already exists. Read `package.json`, key source directories, and any existing ideation history in `.agileflow/ideation/`.
+
+3. **Brainstorm phase.** Generate 10–15 ideas across these categories:
+   - Feature gaps (things similar products have that this one doesn't)
+   - UX improvements (friction points in existing flows)
+   - Growth opportunities (viral loops, referral mechanics, power user features)
+   - Integration opportunities (third-party services that would add value)
+   - Technical improvements that unlock user value (performance, reliability)
+
+4. Present the ideas in a ranked list. Ask the user: [A] Generate a product brief for [idea], [B] Research [idea] more deeply, [C] Brainstorm more in a specific category, [D] Browse ideation history.
+
+5. If the user picks an idea for a brief, run the ideate-brief sub-workflow: expand the idea into a full product brief with problem statement, proposed solution, user stories, success metrics, and effort estimate.
+
+6. Save the session to `.agileflow/ideation/<timestamp>-session.md` with the topic, generated ideas, and any briefs created.
+
+7. Ask: [A] Create an Epic from this brief (recommended if ready to plan), [B] Save as ideation history for later, [C] Run the feature brainstorm audit for deeper analysis.
+
+## Output
+
+Ranked list of ideation ideas. Optional product brief for selected idea. Session saved to `.agileflow/ideation/`. Optional Epic created.
+
+## Fallbacks
+
+**If interactive prompts (AskUserQuestion) are unavailable:**
+Present options as a numbered list in your response. Ask the user to reply with a number. Example:
+
+```
+How would you like to proceed?
+1. Fix the P0 findings now
+2. Review full findings first
+3. Export report only
+```
+
+**If agent spawning (Task tool / multi-agent) is unavailable:**
+Perform each analysis inline and sequentially instead of spawning parallel agents.
+Work through the key checks for each domain yourself using the reference files in `references/`.
+Consolidate findings into the same structured output format — the user gets the same result, just slower.