crowi-design

Turns design ideas into reviewed RFCs or implementation-ready specs via multi-agent workflows.

1.1k|165|Updated Aug 18, 2014
One-click install
npx skills add https://github.com/crowi/crowi --skill crowi-design
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: crowi-design
Source: https://github.com/crowi/crowi/tree/main/.claude/skills/crowi-design
Command: npx skills add https://github.com/crowi/crowi --skill crowi-design

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Designing a new feature or architecture for the Crowi wiki requires deep codebase research, prior-art analysis, adversarial review, and careful documentation — work that overloads a single AI session and often produces shallow specs. This Skill orchestrates that entire pipeline while keeping the main conversation lightweight.

Core Features & Use Cases

  • Two-phase Workflow orchestration: Phase A researches the codebase, prior decisions, and external prior art in parallel, then synthesizes 2-3 design approaches with an RFC-vs-spec recommendation; Phase B writes the document and runs adversarial multi-lens reviews with a bounded revise loop.
  • Human decision gate: Design convergence (approach selection, RFC vs spec, open questions) happens through an interactive gate, so judgment stays with the user while heavy lifting runs in subagents.
  • Codex offload with fail-open fallback: Analysis, writing, and review stages run through codex-run.sh on tiered models and automatically fall back to Claude agents when Codex is unavailable, with every fallback reported.
  • Use Case: Ask to design a new Markdown notation for Crowi; the Skill researches the renderer pipeline, proposes approaches, lets you pick one, then produces an adversarially reviewed implementation-ready spec that the crowi-feature skill can implement directly.

Quick Start

Ask the AI to run /crowi-design followed by your design topic, for example to design image display attributes for the wiki renderer.

Frequently Asked Questions about crowi-design

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

FAQPage Schema
How do I turn a design idea into an RFC or spec with this skill?

Run /crowi-design followed by your topic. The skill researches the codebase and prior art, presents 2-3 design approaches in an interactive gate, then writes and adversarially reviews the chosen RFC or spec until it passes review.

What is the difference between the RFC and spec outputs?

An RFC is an English document committed to docs/rfcs/ for large cross-cutting design decisions and OSS precedent. A spec is a Japanese implementation-ready document in .feature-state/specs/ following spec contract v2, with path-level implementation maps and acceptance-criteria-to-test mappings.

Can I review an existing spec or RFC without writing a new one?

Yes. Run /crowi-design review followed by the document path. This invokes the review workflow in reviewOnly mode, running the adversarial lens panel once and returning structured findings, blocking issues, and preexisting problems.

What happens when Codex is unavailable during a design run?

Every Codex stage fails open to an equivalent Claude agent implementation, and each fallback is recorded in codexFallbacks. If too many review lenses run degraded in one round, the workflow returns DEGRADED instead of a verdict so the result is not silently trusted.

When should I not use this design workflow?

Skip it for trivial specs you can write directly, for work already in implementation (use code review instead), and for single-pass validation of an existing spec, which is handled by the dedicated spec-review entry point.