Design structured backend and frontend tasks for ArenaQuest.
npx skills add https://github.com/RaphaelSilva/ArenaQuest --skill task-writer
Please help me install this Agent Skill. Skill: task-writer Source: https://github.com/RaphaelSilva/ArenaQuest/tree/main/.agents/skills/task-writer Command: npx skills add https://github.com/RaphaelSilva/ArenaQuest --skill task-writer
This Skill addresses the need for creating detailed and well-structured technical tasks, facilitating a seamless and efficient workflow in ArenaQuest's backend and frontend development processes.
As an AI, initiate the task creation process by specifying the requirement or feature for which the task is needed, for example: "Act as task-writer, write tasks for the user enrollment feature."
High-intent search queries and answers about installing and using this skill.
To write structured technical tasks, you need standardized templates that separate backend and frontend concerns, ensuring clear sections for requirements, dependencies, constraints, and verification. This approach enforces maintainability and scalability standards.
Separating backend and frontend tasks requires defining clear task patterns and distinct standardized templates for each domain. This ensures proper separation of concerns and organizes dependencies effectively across the development workflow.
Organizing task files for dependency management requires specific file location and naming guidelines. Establishing a standardized directory structure allows teams to easily track task progress and map upstream or downstream dependencies.
Yes, creating technical documentation and tasks requires adherence to internal coding standards and specification guidelines. Enforcing these standards during task creation ensures the resulting development work maintains scalability and maintainability.
Yes, standardized task templates support complex feature planning by providing dedicated sections for constraints and verification. Structuring tasks this way ensures all requirements and dependencies are captured before development begins.
Task creation without separation of constraints fails because it mixes backend and frontend dependencies, leading to unclear requirements and verification criteria. Maintaining strict separation ensures tasks remain actionable and aligned with internal standards.
ZiphyrienReads .trellis/spec/ guidelines and injects them into task context before coding.
gmliaoCreate detailed technical implementation plans from functional specifications and technology stacks.
offers-pngCreate and manage persistent project tasks with dependencies across sessions.
KeyValueSoftwareSystemsSynthesize product requirement documents from unstructured inputs into prd.md.
