一键在 Manus 中运行任何 Skill

hoyeon-specify

星标169

分支21

更新时间2026年5月15日 07:10

Hoyeon requirements workflow for Codex. Use when the user invokes "$hoyeon-specify" or wants to turn an unclear goal into structured requirements.md for Hoyeon. This adapter loads the canonical specify skill and follows its Codex runtime surface.

安装

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

在 Manus 中运行

来源

team-attention

team-attention/hoyeon

打开 GitHub 仓库查看创作者相关仓库

下载

在 Manus 中运行

hoyeon-specify

This is the Codex-facing wrapper for Hoyeon's canonical specify skill.

Canonical skill:

Installed root: __HOYEON_PLUGIN_ROOT__/skills/specify/SKILL.md
Repo-local fallback: skills/specify/SKILL.md from the current Hoyeon repo

When this skill is invoked:

Read the canonical skill file above before executing the workflow.
Follow the Runtime Surface -> Codex section in that file.
Keep durable state changes Bash-first through hoyeon-cli.
Do not rely on hooks or MCP for Codex v1.
Use Hoyeon native-agent adapter names when dispatching subagents: hoyeon-code-explorer, hoyeon-worker, hoyeon-verifier, and hoyeon-code-reviewer.

Interview obligation (Codex)

The canonical skill is written around the AskUserQuestion tool, which Codex does not have. Lack of AskUserQuestion is NOT a license to skip the interview. You must still elicit user intent before writing requirements.md.

Rules:

Ask one concise plain-text question at a time. Wait for the user's reply before continuing. Do not batch multiple questions into one turn unless they are trivially orthogonal yes/no items.
Phase 0.1 Mirror is mandatory — present your understanding (goal, non-goal, ambiguous) and ask the user to approve or revise before proceeding.
Phase 0.2 WHERE inference is mandatory — infer PROJECT_TYPE, SITUATION, AMBITION, RISK factors from the repo, present the "Inferred Context" block with evidence and confidence, and ask the user to confirm or override.
Any dimension marked low confidence (typically AMBITION on a truly new project) MUST be asked explicitly. Do not silently default.
Phase 1 axis interviews still apply. Convert each AskUserQuestion prompt in the canonical skill into a plain-text question that lists the same options inline (e.g., "Who is the primary user? (a) Senior developers, (b) Junior developers, (c) Both — or describe your own.").
Phase 4 Confirmation is mandatory — show the requirements preview and get explicit user approval before overwriting requirements.md.

If the user repeatedly answers "you decide" or "whatever works", follow the canonical "I don't know" protocol (tentative judgment + Open Decision entry), not silent inference.

The output contract remains the canonical Hoyeon contract: <spec_dir>/requirements.md.

同仓库更多 Skills

同仓库

verify

team-attention/hoyeon

Run a full implementation verification pass after code or data changes. Use when the user asks to verify, QA, smoke test, run checks, validate a feature, inspect a local app in the browser, capture screenshots, or turn discovered QA issues into regression tests/checklists with user approval.

2026-05-19169

hoyeon-execute

team-attention/hoyeon

Hoyeon execution workflow for Codex. Use when the user invokes "$hoyeon-execute" or wants to execute a Hoyeon plan.json through the Bash-first Codex adapter. This adapter loads the canonical execute skill and follows its Codex runtime surface.

2026-05-17169

execute

team-attention/hoyeon

Plan-driven orchestrator. Reads plan.json (from /blueprint) or requirements.md, then dispatches workers to build the system. Use when: "/execute", "execute", "plan 실행", "blueprint 실행"

2026-05-17169

browser-work

team-attention/hoyeon

Recon-first browser automation. Orchestrator explores the site first via chromux, saves a guide file with insights, then delegates execution to browser-explorer agent. Use when: "/browser-work", "브라우저 작업", "사이트에서 해줘", "웹에서 해줘", "LinkedIn에서", "크롬으로", "browser task", "automate this site".

2026-05-15169

deep-research

team-attention/hoyeon

Deep web research skill using parallel subagents + chromux browser-explorer + Gemini. Spawns multiple WebSearch research agents AND browser-explorer agents (via chromux for JS-heavy/dynamic sites), plus a Gemini CLI deep research source, then synthesizes everything into a cited report. Uses WebSearch, WebFetch, chromux browser-explorer, and Gemini CLI. Invoke with /deep-research <topic>.

2026-05-15169

team-attention/hoyeon

Systematically QA test any application — web apps, native macOS apps, Electron apps, CLI tools, interactive REPLs, or anything on screen. Three modes: browser (chromux/CDP, fast, DOM-level), computer (MCP computer-use, screenshot + pixel clicks, any app), and cli (tmux, send-keys + capture-pane for interactive terminals). Auto-selects mode or accepts --browser / --computer / --cli override. Use when asked to "qa", "QA", "test this site", "test this app", "find bugs", "test and fix", "fix what's broken", "dogfood", "exploratory test", "bug hunt", "QA this app", "사이트 테스트", "앱 테스트", "브라우저 QA", "화면 보고 테스트해줘", "네이티브 앱 테스트", "screen test". Three tiers: Quick (critical/high only), Standard (+ medium), Exhaustive (+ cosmetic). Produces before/after health scores, fix evidence, and a ship-readiness summary.

2026-05-15169

name	hoyeon-specify
description	Hoyeon requirements workflow for Codex. Use when the user invokes "$hoyeon-specify" or wants to turn an unclear goal into structured requirements.md for Hoyeon. This adapter loads the canonical specify skill and follows its Codex runtime surface.

hoyeon-specify

This is the Codex-facing wrapper for Hoyeon's canonical specify skill.

Canonical skill:

Installed root: __HOYEON_PLUGIN_ROOT__/skills/specify/SKILL.md
Repo-local fallback: skills/specify/SKILL.md from the current Hoyeon repo

When this skill is invoked:

Read the canonical skill file above before executing the workflow.
Follow the Runtime Surface -> Codex section in that file.
Keep durable state changes Bash-first through hoyeon-cli.
Do not rely on hooks or MCP for Codex v1.
Use Hoyeon native-agent adapter names when dispatching subagents: hoyeon-code-explorer, hoyeon-worker, hoyeon-verifier, and hoyeon-code-reviewer.

Interview obligation (Codex)

Rules:

Ask one concise plain-text question at a time. Wait for the user's reply before continuing. Do not batch multiple questions into one turn unless they are trivially orthogonal yes/no items.
Phase 0.1 Mirror is mandatory — present your understanding (goal, non-goal, ambiguous) and ask the user to approve or revise before proceeding.
Phase 0.2 WHERE inference is mandatory — infer PROJECT_TYPE, SITUATION, AMBITION, RISK factors from the repo, present the "Inferred Context" block with evidence and confidence, and ask the user to confirm or override.
Any dimension marked low confidence (typically AMBITION on a truly new project) MUST be asked explicitly. Do not silently default.
Phase 1 axis interviews still apply. Convert each AskUserQuestion prompt in the canonical skill into a plain-text question that lists the same options inline (e.g., "Who is the primary user? (a) Senior developers, (b) Junior developers, (c) Both — or describe your own.").
Phase 4 Confirmation is mandatory — show the requirements preview and get explicit user approval before overwriting requirements.md.

If the user repeatedly answers "you decide" or "whatever works", follow the canonical "I don't know" protocol (tentative judgment + Open Decision entry), not silent inference.

The output contract remains the canonical Hoyeon contract: <spec_dir>/requirements.md.