feat: optimize skill prominence in workflows

- Move skill instructions to top of each phase block
- Make skill instructions concise: 'Apply your X skill. If unavailable, ask user about X practices.'
- Reduce verbosity while maintaining clear directive language
- Skills now lead each phase with fallback to user consultation

Author: mrsimpson

resources/workflows/skilled-bugfix.yaml

@@ -44,8 +44,8 @@ states:
     default_instructions: |
       Examine the code paths involved in the bug, identify the root cause, and understand why the issue occurs. Use debugging tools, add logging, and trace through the problematic code.
 
-      - Use your **architecture** skill if available, or ask the user about their architectural conventions
-      - Use your **application-design** skill if available, or ask the user about their application design practices
+      - **Apply your architecture skill.** If unavailable, ask user about architectural conventions.
+      - **Apply your application-design skill.** If unavailable, ask user about application design practices.
 
       Document your analysis and create tasks as needed.
     transitions:
@@ -74,9 +74,9 @@ states:
     default_instructions: |
       Implement the solution based on your analysis:
 
+      - **Apply your coding skill.** If unavailable, ask user about coding practices.
+      - **Apply your testing skill.** If unavailable, ask user about testing practices.
       - Check whether there is a design document in the project and follow it
-      - Use your **coding** skill if available, or ask the user about their coding practices and patterns
-      - Use your **testing** skill if available, or ask the user about their testing practices
 
       Before implementing, assess the approach:
       - How critical is this system? What is the blast radius if the fix causes issues?
@@ -109,7 +109,7 @@ states:
     default_instructions: |
       Test the fix thoroughly to ensure the original bug is resolved and no new issues were introduced.
 
-      - Use your **testing** skill if available, or ask the user about their testing practices
+      - **Apply your testing skill.** If unavailable, ask user about testing practices.
       - Verify the solution is robust and handles edge cases
     transitions:
       - trigger: 'fix_needs_adjustment'
@@ -154,7 +154,7 @@ states:
       - Ask the user to review document updates
 
       **STEP 3: Final Validation**
-      - Use your **testing** skill if available, or ask the user about their testing practices
+      - **Apply your testing skill.** If unavailable, ask user about testing practices.
       - Verify documentation accuracy with a final review
       - Ensure bug fix is ready for production
       - Update task progress and mark completed work as you finalize the bug fix

resources/workflows/skilled-epcc.yaml

@@ -28,11 +28,11 @@ states:
     default_instructions: |
       Research the codebase to understand existing patterns and gather context about the problem space.
 
+      - **Apply your starting-project skill.** If unavailable, ask user about project setup practices.
+      - **Apply your architecture skill.** If unavailable, ask user about architectural conventions.
       - If uncertain about conventions or rules, ask the user about them
       - Read relevant files and documentation
-      - Check whether there is a requirements document in the project and if so, read it carefully
-      - If the project is still empty, use your **starting-project** skill if available, or ask the user about their project setup practices
-      - Use your **architecture** skill if available, or ask the user about their architectural conventions
+      - Check whether there is a requirements document in the project and if so, read it carefully)
 
       Focus on understanding without writing code yet. Document your findings and create tasks as needed.
     transitions:
@@ -46,10 +46,10 @@ states:
     default_instructions: |
       Create a detailed implementation strategy based on your exploration:
 
+      - **Apply your architecture skill.** If unavailable, ask user about architectural conventions.
+      - **Apply your application-design skill.** If unavailable, ask user about application design practices.
       - Check whether there is a requirements document in the project and base your strategy on it
       - Check whether there is a design document in the project and adhere to it; if not, elaborate design options and present them to the user
-      - Use your **architecture** skill if available, or ask the user about their architectural conventions
-      - Use your **application-design** skill if available, or ask the user about their application design practices
 
       Break down the work into specific, actionable tasks. Consider edge cases, dependencies, and potential challenges. Document the planning work thoroughly and create implementation tasks as part of the code phase as needed.
     transitions:
@@ -80,10 +80,10 @@ states:
     default_instructions: |
       Follow your plan to build the solution:
 
+      - **Apply your coding skill.** If unavailable, ask user about coding practices.
+      - **Apply your testing skill.** If unavailable, ask user about testing practices.
       - Check whether there is a design document in the project and follow it; if not, elaborate design options and present them to the user
       - Check whether there is a requirements document in the project and ensure all requirements are met
-      - Use your **coding** skill if available, or ask the user about their coding practices and patterns
-      - Use your **testing** skill if available, or ask the user about their testing practices
 
       Write clean, well-structured code with proper error handling. Prevent regression by building, linting, and executing existing tests. Stay flexible and adapt the plan as you learn more during implementation. Update task progress and create new tasks as needed.
     transitions:
@@ -150,7 +150,7 @@ states:
 
       **STEP 3: Final Validation**
 
-      - Use your **testing** skill if available, or ask the user about their testing practices
+      - **Apply your testing skill.** If unavailable, ask user about testing practices.
       - Verify documentation accuracy with a final review
       - Ensure code is ready for production/delivery
 

resources/workflows/skilled-greenfield.yaml

@@ -28,13 +28,14 @@ states:
     description: 'Deep requirements discovery and PRD creation phase'
     default_instructions: |
       Understand WHAT the system should do, WHO will use it, WHY it's needed, and WHAT'S in/out of scope by exploring:
+
+      **Apply your starting-project skill.** If unavailable, ask user about project setup practices.
+
       - Are there existing solutions? What gaps do they have?
       - What technologies must/cannot be used? Why?
       - How will you measure product success?
       - Have you validated this need with potential users?
 
-      Use your **starting-project** skill if available, or ask the user about their project setup practices and conventions.
-
       Don't discuss technical implementation yet - focus purely on understanding the problem space and requirements. Check whether there is a requirements document in the project and if so, read it carefully. Create tasks as needed.
     transitions:
       - trigger: 'ideation_complete'
@@ -51,11 +52,11 @@ states:
     default_instructions: |
       Design the technical solution based on the requirements discovered during ideation.
 
+      - **Apply your architecture skill.** If unavailable, ask user about architectural conventions.
       - Ask about the user's technical preferences and experience
       - Challenge their choices by presenting alternatives
       - Evaluate pros and cons of different tech stacks, frameworks, and architectural patterns
       - Consider non-functional requirements like scalability, performance, maintainability, and deployment
-      - Use your **architecture** skill if available, or ask the user about their architectural conventions
 
       Check whether there is an architecture document in the project and if so, read and build on it. Don't start coding yet - focus on technical design decisions.
     transitions:
@@ -87,7 +88,7 @@ states:
     default_instructions: |
       Create a detailed implementation strategy based on your completed architecture and requirements.
 
-      - Use your **application-design** skill if available, or ask the user about their application design practices
+      - **Apply your application-design skill.** If unavailable, ask user about application design practices.
       - Check whether there is a design document in the project and adhere to it
 
       **STEP 1: Break Down Work**
@@ -126,10 +127,10 @@ states:
     default_instructions: |
       Build the solution following your plan and architecture.
 
+      - **Apply your coding skill.** If unavailable, ask user about coding practices.
+      - **Apply your testing skill.** If unavailable, ask user about testing practices.
       - Check whether there is a design document in the project and follow it
       - Check whether there is a requirements document in the project and ensure all requirements you are currently working on are met
-      - Use your **coding** skill if available, or ask the user about their coding practices and patterns
-      - Use your **testing** skill if available, or ask the user about their testing practices
       - Write clean, well-structured code with proper error handling
       - Prevent regression by building, linting, and executing existing tests
       - Stay flexible and adapt the plan as you learn more during implementation, but maintain alignment with your architecture decisions
@@ -186,7 +187,7 @@ states:
       Ensure project has complete documentation for newcomers including setup, usage, architecture overview, and contribution guidelines.
 
       **STEP 4: Final Validation**
-      - Use your **testing** skill if available, or ask the user about their testing practices
+      - **Apply your testing skill.** If unavailable, ask user about testing practices.
       - Verify documentation accuracy with a final review
       - Ensure project is ready for users and contributors
       - Update task progress and mark completed work as you finalize the project