Ijfw Workflow

Universal project workflow with built-in quality auditing. Quick mode (fast brainstorm, ~5 min) or Deep mode (full plan with audits, ~30 min). Auto-picks based on task size. Trigger: 'build', 'create', 'plan', 'new project', 'brainstorm', 'design', 'UI', 'website', 'dashboard', 'app', 'help me build', or any project-level task.

43 stars 17 forksProductivity & Notes

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add FerroxLabs/wayland-core --skill ijfw-workflow
Manual install
git clone --depth 1 https://github.com/FerroxLabs/wayland-core.git /tmp/wayland-core
mkdir -p ~/.claude/skills
cp -r /tmp/wayland-core/crates/wayland-ijfw/snapshots/ijfw-source/claude/skills/ijfw-workflow ~/.claude/skills/ijfw-workflow

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# IJFW Workflow

Two modes, same principles, same invariants.

- **Quick** -- 5 moves, 3-5 minutes, locked brief. For features, fixes, ideas.
- **Deep** -- 6 required modules + 3 optional, 20-45 minutes. For new projects, major refactors, launches.

```
Donahoe Loop: BRAINSTORM -> PLAN -> EXECUTE -> VERIFY -> SHIP -> MEASURE
              |<--- memory recall at every entry --->|
              |<--- Trident cross-audit on request --->|
```

## RUNTIME BOOTSTRAP AND FALLBACKS

Before the first workflow write or command invocation, inspect whether
`.ijfw/memory/` exists so the auto-picker and empty-state opener can use that
signal accurately. Then ensure `.ijfw/memory/` and `.planning/` exist before
writing artifacts. If the `ijfw` CLI is unavailable in this session, continue
with markdown files and visible chat checklists, then state the exact CLI
command the user can run later. Optional commands such as `ijfw cross`,
`ijfw design`, `ijfw recover`, `ijfw blackboard`, `ijfw team`, and `ijfw swarm`
must degrade to explicit written artifacts instead of blocking the workflow.

---

# AUTO-PICKER (runs first, every time)

Deterministic signals, visible reasoning, no friction.

| Signal | Points towards |
|---|---|
| Prompt < 15 words | Quick |
| Prompt has clear verb + object | Quick |
| Vague verbs alone ("improve", "fix", "handle", "deal with") | Deep |
| "New project", "major refactor", "launch", "design" | Deep |
| Project dir has no `.ijfw/memory/` | Deep |
Read the full skill on GitHub

Details

Skill name
ijfw-workflow
Path
crates/wayland-ijfw/snapshots/ijfw-source/claude/skills/ijfw-workflow/SKILL.md
License
Apache-2.0
Repo updated
3 November 2026

FAQ

What does the Ijfw Workflow skill do?

Universal project workflow with built-in quality auditing. Quick mode (fast brainstorm, ~5 min) or Deep mode (full plan with audits, ~30 min). Auto-picks based on task size. Trigger: 'build', 'create', 'plan', 'new project', 'brainstorm', 'design', 'UI', 'website', 'dashboard', 'app', 'help me build', or any project-level task.

How do I install the Ijfw Workflow skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add FerroxLabs/wayland-core --skill ijfw-workflow. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Ijfw Workflow popular?

It lives in FerroxLabs/wayland-core, which has 43 GitHub stars and 17 forks.

Related skills

Browse the most popular Claude skills, all productivity & notes skills, or write your own with the skills generator.