菜单
Full autonomous feature implementation from customer spec to PR. Use when user provides a customer spec (file path, inline text, or ticket reference) and wants end-to-end implementation including spec/plan artifacts, feature branch, coding, verification, commits, and PR creation.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Run and drive the jedlik-nejedlik Nuxt site. Use when asked to start the dev server, build, verify a change in the real app, or screenshot a page. Verify with agent-browser yourself; xdg-open only when the user wants to look.
Download a Google Doc as markdown and turn it into an .aiwork spec ready for the `implement-spec-to-pr` skill. Detects inline editor notes (e.g. "Přeformulovala bych", "KLIKACÍ TLAČÍTKO", "@@", strike-through remarks) and converts them into `<!-- TODO: ... -->` markdown comments so the implementer sees them as actionable items. Trigger when the user pastes a docs.google.com URL and wants to import it as a spec, or says "stáhni gdoc", "import gdoc", "gdoc as spec", "gdoc → spec".
Vue/Nuxt code conventions for SFC structure, props, state, template directives, and composables. Load whenever writing or editing Vue Single-File Components (.vue) or Nuxt-specific code anywhere in this repo — components, pages, layouts, composables, or plugins.
Monitor Coolify deployment of jedlik-nejedlik-production triggered by git push. Streams build logs, filters errors live, checks final status, and suggests fixes if deployment failed. Use when user says "monitor deploy", "watch deployment", "check deploy", or after pushing to master.
| name | implement-spec-to-pr |
| description | Full autonomous feature implementation from customer spec to PR. Use when user provides a customer spec (file path, inline text, or ticket reference) and wants end-to-end implementation including spec/plan artifacts, feature branch, coding, verification, commits, and PR creation. |
| allowed-tools | Bash, Read, Write, Edit, Glob, Grep, Task, WebFetch, Skill |
| argument-hint | <path-to-spec | inline text> |
date +%Y-%m-%ddate +%H-%Mgit branch --show-currentgit status --shortRead $ARGUMENTS (file path or inline text). Generate a kebab-case slug from it.
Create .aiwork/{date}_{slug}/spec.md per the .aiwork protocol.
First, copy the FULL original text into a blockquote. This is a mechanical paste - never summarize, truncate, or rephrase.
Then write analysis sections: summary, decisions table (Decision | Choice | Rationale), scope (in/out), acceptance criteria. Mark ambiguous points [DECIDED].
Create feature branch. Explore codebase for similar patterns and conventions. Use MCP tools for external services if available.
For complex tasks, write plan.md next to spec with numbered implementation steps. Mark unclear items [OPEN].
Execute plan. Use Task agents for parallel independent work.
Improve all rendered text with /czech-typography skill.
Visual check in the browser.
Commit changes (split if logically separate).
Ask whether to create a PR.
If yes: Create PR with gh pr create (summary, changes, acceptance criteria). Push.
Output report: branch, PR URL, files changed, verification status, open questions.