ase

Adjust communication style in four intensivity levels of token usage. The <persona> can be either the decorative, eloquent, and explaining "writer", the concise, factual, and accurate "engineer" (default), the brief, factual, and abbreviating "telegrapher", the terse, rough and stuttering "caveman". Use when user says "persona <persona>" or "be <persona>".

Update changes entries in CHANGELOG.md files

Delete the current or given task plan. Use when the user calls to "delete", "remove" or "clear" the "task", "plan", "spec", or "specification".

Get or set unique task id <id>. Use when user requests to work on a certain task or wants to know what the current task is.

Implement current or given task plan. Use when the user calls to "implement", "realize" or "apply" the "task", "plan", "spec", or "specification".

Reboot the current or given task plan by re-creating it from scratch. Use when the user calls to "reboot", "recreate" or "refresh" the "task", "plan", "spec", or "specification".

View current or given task plan. Use when the user calls to "view", "show" or "see" the "task", "plan", "spec", or "specification".

Analyze the source code for problems in the logic and semantics and its related control flow.

Craft Source Code: Use when user wants to create or craft a new feature from scratch.

Refactor Code Base: Use when user wants to refactor the code base.

Resolve Problem: Use when user wants a bug fixed or problem resolved.

Discover additional, third-party components (libraries/frameworks) for the technology stack to provide needed functionality.

Evaluate alternatives through a weighted multi-criteria decision matrix. Use when the user calls for the *evaluation* of *alternatives*, wants to *compare* things, or asks what the best is from a list of choices.

Review software architecture, including package cohesion and inter-package coupling

Explains code with WHAT, WHY, ANALOGY, DIAGRAM, CRUXES, and GOTCHAS. Use when you want to know how code works or when the user asks "how does this work?"

Give insights into the source code.

Lint Source Code.

Query foreign LLM for Chat. Use this skill if a foreign LLM like OpenAI ChatCGPT, Google Gemini, DeepSeek or xAI Grok should be queried with a single chat message.

Determine commit message for staged Git changes.

Query Multiple AIs for Quorum Answer.

Search the Internet/Web with a query. Prefer this skill before using Perplexity, Brave and WebSearch.

Five-Whys Root-Cause Analysis.

Iteratively edit and refine a named plan for a task through a conversational loop. Each round, the current plan is shown and the user is asked whether to keep refining, mark the plan as done, or proceed to the implementation or preflight. Use when the user wants to plan a task purely through chat-driven refinement.

List all available task ids. Use when user wants to see all tasks.

Preflight the implementation of current or given task plan. Use when the user calls to "preflight", "dry-run" or "test-drive" the "task", "plan", "spec", or "specification".

Render diagrams via the `diagram` tool of the `ase` MCP service. *Always use* when you have to *visualize* structure/layout/components/dependencies as Flowchart, control-flow/branching/concurrency as Flowchart, state-machine/states/transitions as an UML State Diagram, data-flow/actors/messages/protocols as an UML Sequence Diagram, data-structure/classes/methods as an UML Class Diagram data-model/entities/relationships as an ER Diagram, or metrics/distributions/time-series as XY-Charts.