arnesto

Use when asked to "shape up", "run a shaping session", "set an appetite", "scope a project without estimates", "betting table", or "ship in fixed cycles". Helps teams escape estimate-driven development and Scrum fatigue. The Shape Up method (created by Ryan Singer at Basecamp/37signals) uses fixed time boxes, variable scope, and collaborative shaping to ship meaningful work predictably.

Save, back up, or share the current project on Cursor — creates a repo (a saved, versioned copy that isn't public) even for users who have never used git, handling all setup automatically. Use when the user asks to save, back up, publish, or share their project on Cursor, or how to not lose it.

Runs the rest of a /shell request as a literal shell command. Use only when the user explicitly invokes /shell and wants the following text executed directly in the terminal.

Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.

Design, organize, evaluate, benchmark, and improve portable Agent Skills. Use when creating a new skill, deciding whether a workflow deserves a skill, auditing a skill library, comparing a skill against baseline or prior versions, optimizing a skill description for better triggering, or retiring outdated skills across Claude, Codex, ChatGPT-compatible tools, and other Agent Skills-compatible environments.

Design, organize, evaluate, benchmark, and improve portable Agent Skills. Use when creating a new skill, deciding whether a workflow deserves a skill, auditing a skill library, comparing a skill against baseline or prior versions, optimizing a skill description for better triggering, or retiring outdated skills across Claude, Codex, ChatGPT-compatible tools, and other Agent Skills-compatible environments.

Use this to fix and re-install agent skills that have failed installation. This skill provides the necessary context and permissions to surgically update the `manifest.json` after a fix has been applied.

Small Safe Steps (S3): breaks work into 1-3h increments with zero downtime. Use when asking "how do I implement/migrate/refactor", "what steps to do X", "plan safe migration", or handling risky DB/API changes. Applies expand-contract pattern for migrations, refactorings, schema changes.

Investigate and fix bugs in a company environment using available tickets, internal documentation, private repositories, ownership data, and production evidence. Use for corporate or internal engineering incidents that span systems such as Jira, Confluence, Slack, Drive, GitHub, or enterprise monorepos; use diagnose for ordinary repository-local debugging.

Split current work into small reviewable PRs. Use when the user asks to split a chat, set of changes, branch, or PR.

Create compelling progress updates and release notes. Use when shipping a new feature or need to communicate progress to stakeholders.

Configure a custom status line in the CLI. Use when the user mentions status line, statusline, statusLine, CLI status bar, prompt footer customization, or wants to add session context above the prompt.

Write or rewrite text in ASD-STE100 Simplified Technical English. ONLY use this skill when the user explicitly invokes it by name — i.e. they type "/ste" or literally write "use the ste skill" / "apply ASD-STE100". Do NOT trigger it on paraphrased intent such as "simplify this", "make it clearer", "write technical documentation", or "shorter sentences please" — the user has deliberately scoped this skill to explicit invocation only. For those requests, respond normally without loading this skill unless they name it.

Suggests manual context compaction at logical intervals to preserve context through task phases rather than arbitrary auto-compaction.

Use when asked to "strategic narrative", "Andy Raskin", "tell our company story", "write a pitch deck", "explain why customers should care", or "movement narrative". Helps craft compelling narratives that define movements rather than just selling products. The Strategic Narrative framework (created by Andy Raskin) transforms pitches from feature lists into stories about change.

Coaches through Rumelt's Strategy Kernel to build sound strategy. Use when defining strategy, diagnosing strategic challenges, or creating strategic plans.

Enforce consistent tagging across the Obsidian wiki using a controlled vocabulary. Use this skill when the user says "fix my tags", "normalize tags", "clean up tags", "tag audit", "what tags should I use", "tag taxonomy", or whenever you're creating or updating wiki pages and need to choose the right tags. Also trigger when the user asks about tag conventions, wants to add a new tag to the taxonomy, or says "my tags are a mess". Always consult this skill's taxonomy file before assigning tags to any wiki page.

Test-driven development with red-green-refactor loop. Use when user wants to build features or fix bugs using TDD, mentions "red-green-refactor", wants integration tests, or asks for test-first development.

Select and implement the right test double with a default preference for fakes, stubs, and spies over mocks. Use when writing or refactoring tests, especially when users mention test doubles, mocking strategy, interaction assertions, or flaky tests caused by over-mocking.

Applies Kent Beck's Thinkies—pattern-based thinking habits that generate ideas. Use when stuck, exploring alternatives, or reframing decisions.