Agent skill

task

Create well-defined task specifications from plans or user prompts. Use when user wants to define a task, create a work item, break down a plan into actionable work, or write a spec for implementation. Triggers on "create task", "define task", "write spec", "break this down", "make this actionable", or when moving from planning to execution.

View SKILL.md on GitHub Repository
Stars 27
Forks 4

Install this agent skill to your Project

npx add-skill https://github.com/frmlabz/frm-stack/tree/main/capabilities/general/skills/task

SKILL.md

Task Creation

Create well-defined task specifications that provide clear goals while leaving implementation open to interpretation. Output to .work/tasks/backlog/<name>.md.

Task Creation Workflow

1. Understand the Scope

Determine task type and relevant sections:

  • Full-stack feature: All sections applicable
  • Backend only: Skip UX Guidelines, focus on System Behaviors and Data
  • Frontend only: Skip Data & Contracts internals, focus on UX
  • Documentation: Summary, Acceptance Criteria only
  • Bug fix: Summary, Edge Cases, Acceptance Criteria
  • Refactor: Summary, System Behaviors, Acceptance Criteria

2. Gather Context

If working from a plan:

  • Read the plan from .work/plans/
  • Extract relevant decisions and constraints
  • Link back to the plan

If working from user prompt:

  • Ask clarifying questions about scope
  • Identify affected files and systems
  • Understand success criteria

3. Write the Task Spec

Create .work/tasks/backlog/<descriptive-name>.md using the template below.

Omit sections not relevant to the task type. A backend API task doesn't need UX Guidelines. A docs update doesn't need System Behaviors.

Task Template

See references/spec-template.md for the full template.

Core sections:

  • Summary: One paragraph describing the task and why it exists
  • User Journey: Entry point, happy path, exit criteria
  • UX Guidelines: What user sees, copy tone, accessibility
  • System Behaviors: Invariants, state transitions, policies
  • Data & Contracts: Storage needs, API/events (high-level)
  • Usage/Cost Accounting: What usage to track and how
  • Edge Cases: Failure modes and user-visible outcomes
  • Acceptance Criteria: Testable outcomes as bullet list

Writing Guidelines

Be Specific About What, Open About How

Good: "User can filter todos by status (all, active, completed)" Bad: "Implement filtering using React state with useMemo optimization"

Define the outcome, not the implementation.

Reference Concrete Touchpoints

Include:

  • Files that will likely need changes
  • API routes or contracts involved
  • Database tables affected
  • UI components to modify

Keep It Scannable

  • Use bullet points over paragraphs
  • Bold key terms
  • Keep acceptance criteria atomic and testable

Task Lifecycle

After creating the task:

  1. Task starts in .work/tasks/backlog/
  2. When work begins, move to .work/tasks/in-progress/
  3. When complete, move to .work/tasks/completed/

Update task status in the file header as work progresses.

Recommended Agent Skills

Expand your agent's capabilities with these related and highly-rated skills.

frmlabz/frm-stack

testing

Shared database testing patterns with testcontainers and Vitest. Use when writing backend tests, setting up test files, debugging test failures, or configuring Vitest. Triggers on "write tests", "test setup", "testcontainers", "vitest config", "test isolation", or when creating new test suites.

27 4
Explore
frmlabz/frm-stack

db-workflow

Database workflow with Postgres, Kysely, and Atlas migrations. Use when modifying database schema, creating migrations, generating TypeScript types, or troubleshooting database issues. Triggers on "schema change", "migration", "db-migrate", "kysely", "atlas", or when editing db/schema.sql.

27 4
Explore
frmlabz/frm-stack

mobile-auth

Better Auth integration with Expo/React Native. Use when working on mobile authentication, session management, or debugging auth issues in the mobile app. Triggers on "mobile auth", "expo auth", "better-auth expo", "session provider", "SecureStore", or when editing apps/frontend/mobile auth files.

27 4
Explore
frmlabz/frm-stack

react-useeffect

React useEffect best practices from official docs. Use when writing/reviewing useEffect, useState for derived values, data fetching, or state synchronization. Teaches when NOT to use Effect and better alternatives.

27 4
Explore
frmlabz/frm-stack

frontend-design

Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML/CSS layouts, or when styling/beautifying any web UI). Generates creative, polished code and UI design that avoids generic AI aesthetics.

27 4
Explore
frmlabz/frm-stack

resolve-pr-comments

Address GitHub PR review comments end-to-end, fetch unresolved review threads (via `gh` GraphQL), implement fixes, reply with what changed, and resolve threads using the bundled scripts. Use when asked to “address PR comments”, “resolve review threads”, or “clear requested changes”.

27 4
Explore

Didn't find tool you were looking for?

Be as detailed as possible for better results