القائمة
Use when starting any new task in the Sake project - ensures structured execution with knowledge discovery, quality checks, and organic growth of the project knowledge base (CLAUDE.md, skills)
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | sake-workflow |
| description | Use when starting any new task in the Sake project - ensures structured execution with knowledge discovery, quality checks, and organic growth of the project knowledge base (CLAUDE.md, skills) |
Structured task execution that grows the project knowledge base organically.
Create a task (TaskCreate) for each numbered step. Mark each as you go.
digraph workflow {
rankdir=TB;
node [shape=box];
discover [label="1. Discover Context"];
brainstorm [label="2. Brainstorm & Plan"];
implement [label="3. Implement"];
verify [label="4. Verify"];
kb_review [label="5a. KB Conformance"];
quality_review [label="5b. Quality Review"];
user_ok [label="User approves?" shape=diamond];
update_kb [label="6. Update Knowledge Base"];
commit [label="7. Commit"];
discover -> brainstorm;
brainstorm -> implement;
implement -> verify;
verify -> kb_review;
kb_review -> quality_review;
quality_review -> user_ok;
user_ok -> update_kb [label="yes"];
user_ok -> implement [label="no"];
update_kb -> commit;
}
Invoke superpowers:brainstorming, then superpowers:writing-plans after design approval.
Skip if trivial (typo, single-line fix, mechanical change with obvious solution).
Follow the plan. Invoke superpowers:executing-plans or work directly.
Loop until all pass:
sake format
sake lint
sake test # or appropriate subset
Fix failures and re-run. Do NOT proceed until green.
Re-read CLAUDE.md and relevant skills. Review your diff for:
Fix any issues found, re-run verify if code changed.
Invoke superpowers:requesting-code-review.
Present results to user, request feedback. If changes needed — return to step 3 or 4.
When: Only after verify passes. If review caused rework, run after subsequent verify.
Update if any of these discovered during work:
What to update:
superpowers:writing-skillsSkip if nothing new was learned.
Conventional commit message per project conventions (see CLAUDE.md).
| Thought | Action |
|---|---|
| "This is too simple for the workflow" | Steps 2-3 can be skipped for trivial tasks, but verify + review still apply |
| "I'll update CLAUDE.md later" | Do it now in step 6, before committing. Later = never |
| "Nothing new to capture" | Double-check: did you read any code to understand it? That understanding may be worth capturing |
| "The skill change is too small to test" | If you changed a skill, verify it reads correctly |
Use when working on CI workflows, GitHub Actions, release process, changelog generation (git-cliff), or dependabot configuration.
Use when working on SakeCLI or SakeCLILibrary targets — CLI entry point, config resolution, SakeAppManager build/run lifecycle, error handling, shell execution.
Use when writing or modifying Sake commands, CommandGroups, SakeApp files, or SakeApp/ directory code. Covers Command struct, dependencies, skipIf, context, storage, subprocess patterns, argument parsing.
Use when working on Sake configuration — .sake.yml, environment variables, CLI options, ConfigManager, ConfigResolver, or adding new config options.
Use when writing or updating Sake documentation — VitePress site structure, existing pages, how to add new docs, documentation conventions.
Use when modifying the @CommandGroup macro in SakeMacros target — SwiftSyntax ExtensionMacro, code generation patterns, testing with assertMacroExpansion.