arkweb-brainstorm

Name: arkweb-brainstorm
Availability: InStock
Author: openharmonyinsight

Decompose ArkWeb requirements into scoped candidates and propose 2-3 feasible design plans.

31|6|Updated Jan 29, 2026

Search Tags:#architecture #technical design #arkweb #prD decomposition #solution options #evidence-based planning #interaction scenarios

Ready to run

npx skills add https://github.com/openharmonyinsight/openharmony-skills --skill arkweb-brainstorm

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: arkweb-brainstorm
Source: https://github.com/openharmonyinsight/openharmony-skills/tree/main/workflows/arkweb/.aceharness/skills/arkweb-brainstorm
Command: npx skills add https://github.com/openharmonyinsight/openharmony-skills --skill arkweb-brainstorm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you break down ArkWeb requirements into clear, feasible technical plan options, so you can move from an unclear PRD to implementable architecture decisions without wasting cycles on guesswork.

Core Features & Use Cases

Requirement Decomposition: Transforms ArkWeb PRD or feature ideas into scoped functional boundaries, constraints, and a structured breakdown.
Evidence-Grounded Solution Design: Produces 2–3 alternative solution plans while forcing alignment to an injected knowledge-base evidence package.
Scenario & Risk Consideration: Analyzes interactive edge cases (e.g., gesture/multi-touch/input-mode differences) and includes risks and estimated effort per plan.

Quick Start

Ask the AI: "Use arkweb-brainstorm to analyze this ArkWeb requirement and output 2-3 feasible方案 with an evidence清单."

Frequently Asked Questions about arkweb-brainstorm

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I decompose an ArkWeb PRD into actionable technical design plans?▼

To decompose an ArkWeb PRD into actionable technical design plans, you can use the arkweb-brainstorm Skill to break down requirements into scoped functional boundaries and generate 2-3 evidence-grounded solution options for implementation planning.

What is the best way to design technical solutions for ArkWeb framework layer modifications?▼

Designing technical solutions for ArkWeb framework layer modifications is best handled by generating 2-3 alternative plans that analyze interactive edge cases like multi-touch differences, while forcing alignment to an injected knowledge-base evidence package to ensure technical feasibility.

Can I analyze ArkWeb API layer requirements without accessing a redundant knowledge base?▼

Yes, you can analyze ArkWeb API layer requirements in subagent mode, which includes safe execution rules that avoid redundant knowledge-base access by pre-injecting the necessary evidence package for grounded requirement splitting.

How do I clarify functional boundaries when splitting unclear ArkWeb feature ideas?▼

To clarify functional boundaries when splitting unclear ArkWeb feature ideas, apply interactive boundary clarification modes to transform raw needs into a structured breakdown, producing a mandatory knowledge evidence checklist to validate the scoped constraints.

Does evidence-based planning work for core and kernel-level ArkWeb modification scenarios?▼

Evidence-based planning works for core and kernel-level ArkWeb modification scenarios by producing structured outputs that include estimated effort and risks per plan, ensuring architecture decisions are grounded in a validated knowledge evidence checklist.