hyperflow-spec
hyperflow-spec guides the design phase of software projects when requests are exploratory, ambiguous, or require architectural decisions. Use it when users employ verbs like brainstorm, design, explore, or ask "what's the best way" rather than "build this now." The skill researches existing code, asks clarifying questions, proposes multiple approaches, then produces a detailed design document at .hyperflow/specs/<slug>.md before handing off to hyperflow-scope for implementation planning.
git clone --depth 1 https://github.com/jeremylongshore/claude-code-plugins-plus-skills /tmp/hyperflow-spec && cp -r /tmp/hyperflow-spec/plugins/ai-agency/hyperflow/templates/antigravity/skills/hyperflow-spec ~/.claude/skills/hyperflow-specSKILL.md
# hyperflow-spec — design phase (Antigravity single-agent) This phase is **thinking, not building**. No code until the design is approved. Follow the `hyperflow` doctrine (autonomy, file-first, AskUserQuestion gates). ## Steps 1. **Research first.** Read the relevant code, `AGENTS.md`, and `.hyperflow/memory/*` if present. Map the affected surface yourself. Do not ask what the code answers. 2. **Ask 2-5 clarifying questions** (floor: 2) via AskUserQuestion — only the *what/which/where* the code can't resolve. Multi-option questions mark one `(Recommended)`; binary ones don't. 3. **Propose 2-3 approaches** with one-line pros/cons/fit each. Recommend one; let the user pick. 4. **Design section-by-section.** Write the design to `.hyperflow/specs/<slug>.md` with this shape: status table → TL;DR (2-3 sentences) → Components → 1. Architecture → 2. Data flow → 3. Key decisions (with trade-offs accepted/rejected) → 4. Edge cases → 5. File structure (created/modified). Present it; ask `Approve all / Revise <section>`. 5. **On approval**, hand off: invoke the `hyperflow-scope` skill with the spec path. ## Rules - Never write implementation code here. - Never inflate a small task into a spec — economy matters. Trivial-clear requests skip straight to `hyperflow-scope`. - The spec file is the artefact; chat shows only a short pointer to it.
Audit and fix Claude Code SKILL.md files to meet enterprise compliance standards. Analyzes frontmatter, required sections, and style. Use when you need to validate or repair skills in a plugin directory.
Learn how SKILL.md files work in Claude Code plugins, then build a production-quality agent skill from scratch. Covers frontmatter schema, body structure, testing, and iteration.
Step-by-step guide to writing a SKILL.md file for Claude Code. Learn how to plan, structure, and test auto-activating skills with proper frontmatter, allowed-tools, dynamic context injection, and supporting files.
|
|
|
|
|