القائمة
Use when implementing a frontend task — produces code that faithfully follows the project's design system and component library.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Divide a specced pastiche task into sub-task GitHub issues with autonomy and dependency labels, mirror them into `_dev/TODO.md`, and update the parent issue. Use after `grill-to-spec` completes for a task, or when the user invokes `/divide-task`.
Convert a completed grill-me session into a spec file. Captures only the task and the decisions locked during grilling — no implementation details, no invented decisions. Use when the user asks to write a spec from a grill, save grill decisions, or after a grill-me session concludes.
Pick up or resume a task from `_dev/TODO.md` — marks `[WIP]`, creates or switches to the task's feature branch, rebases with main. Use when the user invokes `/pick-up-task` or asks to grab/resume a pastiche task.
Rebase the current pastiche feature branch onto main to absorb hotfixes. Use when the user invokes `/rebase-feat-with-main`, when resuming a task, or after a hotfix lands on main while a feature branch is in flight.
Ship a pastiche release — version bump, plugin build, CHANGELOG entry, release commit, tag, GitHub Release, milestone close. Use when the user invokes `/release-pastiche` after a TODO group's final feat→main merge. Human-triggered only; never run from an automated routine.
Use when bootstrapping pastiche for first-time adoption (post-`/pastiche-init`) — fills `KNOWLEDGE.md` and seeds `[GENERAL]` `WISDOM.md` rules section by section. Resumable across sessions; re-invoke to continue.
| name | pastiche |
| description | Use when implementing a frontend task — produces code that faithfully follows the project's design system and component library. |
Orchestrates pastiche-implementer-round1, pastiche-reviewer, and pastiche-implementer-round2 in a bounded loop, then emits a single task report.
Run ls pastiche/FACT.md pastiche/KNOWLEDGE.md pastiche/WISDOM.md. If any are missing, stop and report:
This project does not appear to have pastiche set up — expected
pastiche/{FACT,KNOWLEDGE,WISDOM}.md. Run/pastiche-initto scaffold them.
pastiche-implementer-round1 with {task} → capture {r1_report}.pastiche-reviewer with {task, r1_report} → capture {doubts}. The reply is either one or more lines of <path>#<line> | <comment>, or the literal (no doubts). If any line fails to match the record shape and the output isn't (no doubts), stop and report:
Reviewer returned malformed output; expected
<path>#<line> | <comment>records or the literal(no doubts).
{doubts} is (no doubts), go to 6 (no {r2_report}).pastiche-implementer-round2 with {task, r1_report, doubts} → capture {r2_report}.{r2_report}'s unresolved: block (skip if unresolved: -): Read the file, then Edit to insert a comment in the file's native comment syntax above the targeted <line> (matching surrounding indentation). Comment text: pastiche-unresolved-doubt: <comment from the unresolved: record>.build_command from pastiche/config.yaml. If null or absent, skip. Otherwise run it. For each error, patch using the build output as source of truth. Bounded to 3 patch attempts per error. If an error persists after 3 attempts, leave it and note it in Follow-ups.## Summary
- **Files changed:** <paths> (omit if none)
- **Implementation:** <2–3 sentences describing the end result>
## Follow-ups
- <location> — <one-line description>
- ... (omit section if no follow-ups)
Files changed is the union of files: entries from {r1_report} and {r2_report}; omit the line if both are -.
Follow-up sources (each follow-up bullet must be self-describing; readers shouldn't need to know about rounds, dispositions, or the loop):
{r1_report}'s gaps: line → KNOWLEDGE.md — <scenario>.(knowledge-gap)-tagged record in {r2_report}'s defended: block → KNOWLEDGE.md — <reason>.(wisdom-gap)-tagged record in {r2_report}'s defended: block → WISDOM.md — <reason>.{r2_report}'s unresolved: block → <path>#<line> — <comment>.<path>:<line> — <comment>.