القائمة
Capture a friction point for later pattern analysis
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Collaboratively refine a high-level ambition into a set of chunk prompts.
Migrate the project's ACTIVE chunks to the present-tense, intent-owning standard. Audits each chunk's goal against the code it claims to govern; rewrites retrospective framing inline; logs over-claims that need operator triage; historicalizes chunks with no enduring intent. Designed for full-corpus migrations — fans out across many parallel sub-agents at 5 chunks per agent.
Create a new chunk of work and refine its goal. Use when the operator wants to start new intent-bearing work, chunk something, define a piece of work, or break work into a chunk.
Update code references in the current chunk and move both the PLAN.md and the GOAL.md to the ACTIVE state.
Wake an entity by loading its identity, memories, and operational context
Set up a project steward via interactive interview
| name | friction-log |
| description | Capture a friction point for later pattern analysis |
Capture a friction point quickly—something that slowed you down, confused you, or felt harder than it should be.
$ARGUMENTS
Extract the friction from their observation:
Determine theme: Read docs/trunk/FRICTION.md to see existing themes.
Pick the best fit, or propose a new theme-id if none apply.
Log the entry non-interactively:
ve friction log --title "<title>" --description "<description>" --impact <impact> --theme <theme-id>
For an existing theme, use its theme-id. For a new theme, also provide --theme-name:
ve friction log --title "<title>" --description "<description>" --impact <impact> --theme <new-theme-id> --theme-name "<Theme Display Name>"
Confirm: Tell the operator the entry ID that was created.
Interview the operator with these questions:
"What slowed you down or felt frustrating?"
"How much did this impact your work? (low / medium / high / blocking)"
Read docs/trunk/FRICTION.md to see existing themes, then ask:
"Which theme fits best? [list existing themes] Or describe a new one."
Log the entry non-interactively using their answers:
ve friction log --title "<title>" --description "<description>" --impact <impact> --theme <theme-id>
For a new theme, also provide --theme-name:
ve friction log --title "<title>" --description "<description>" --impact <impact> --theme <new-theme-id> --theme-name "<Theme Display Name>"
Confirm: Tell the operator the entry ID that was created.