Loading...
Loading...
Found 8,783 Skills
Phase 3 of the feature workflow – Complete the acceptance closed-loop. Four tasks: 1. Check layer by layer against {slug}-design.md to verify if the implementation deviates from the plan; fix any deviations on the spot instead of just "noting them" in the report. 2. Incorporate this feature into the project's overall architecture documentation. 3. If this feature changes the user story or boundaries of the corresponding requirement, update the requirement doc accordingly. 4. If this feature originated from a roadmap item, change the status of the corresponding entry in roadmap items.yaml to done and sync it with the main document. Finally, produce a {slug}-acceptance.md as the closed-loop proof for the entire workflow. Prerequisite: cs-feat-impl is completed. Trigger scenarios: User says "The feature is done, let's accept it", "Do the final check", "Prepare for merge", "Generate the acceptance report".
Tomba integration. Manage data, records, and automate workflows. Use when the user wants to interact with Tomba data.
Ikas integration. Manage data, records, and automate workflows. Use when the user wants to interact with Ikas data.
Nordic API Gateway integration. Manage data, records, and automate workflows. Use when the user wants to interact with Nordic API Gateway data.
Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, update or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or iterate on skill quality. Triggers: "create a skill", "make a new skill", "build a skill for", "write a skill that", "skill for doing X", "I want a skill to", "new skill", "design a skill", "scaffold a skill", "improve this skill", "optimize this skill", "this skill isn't working well", "evaluate this skill", "score this skill", "how good is this skill", "run evals on", "benchmark this skill", "test this skill's quality", "skill quality", "skill performance". Also triggers when a user describes a repeatable workflow they want to automate, says "I keep doing X manually", "can you remember how to do X", or "turn this into a skill".
Carbone integration. Manage data, records, and automate workflows. Use when the user wants to interact with Carbone data.
HoloBuilder integration. Manage data, records, and automate workflows. Use when the user wants to interact with HoloBuilder data.
Nextflow DSL 2 TDD implementation workflow. References nextflow-conventions and agent-conduct.
Create new skills, modify and improve existing skills. Use when users want to create a skill from scratch, edit or optimize an existing skill, turn a workflow into a reusable skill, or improve a skill's description for better triggering.
HypeAuditor integration. Manage data, records, and automate workflows. Use when the user wants to interact with HypeAuditor data.
Navigatr integration. Manage data, records, and automate workflows. Use when the user wants to interact with Navigatr data.
Redis Labs integration. Manage data, records, and automate workflows. Use when the user wants to interact with Redis Labs data.