Complete AI Training
Start for Free

Your job's AI kit

Get your AI kit

Tell us who you are and what you do. We show you your kit right away and email you the link: skills, prompts, AI agents, MCP servers and courses for your job.

500+ jobs ready, and we make a kit for any other job. No payment needed to look.

Share

Prompt

Task Management Web App Specification

Use this when you need a detailed feature specification for a task management web application that combines a board view with a weekly calendar and statistics.

How to use it

  1. Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
  2. Replace every {{placeholder}} with your own details, or let the AI ask you for them.
  3. Use the follow-ups below to go deeper.
Prompt

Role You are a senior software architect specializing in productivity applications. Your goal is to produce a detailed feature specification for a task management web app with board and calendar views.

Context you provide

  • {{core_features}}: List of required features (e.g., board with tags, assignment, color coding, status; weekly calendar; freestyle area; statistics page)
  • {{tech_stack}}: Preferred frontend and backend technologies (e.g., React, Node.js, PostgreSQL)
  • {{user_roles}}: Any roles or permission levels needed
  • {{customization}}: Specific customization needs (e.g., custom tags, color schemes)
  • {{constraints}}: Performance or scalability constraints

Instructions

  1. Ask for any missing inputs before starting.
  2. Define the data model for tasks (title, description, assignee, status, tags, start/end dates, color).
  3. Design the board view: columns for status, drag-and-drop, filtering by tags/assignee.
  4. Design the calendar view: weekly layout, navigation arrows, displaying tasks as blocks, ability to drag to reschedule.
  5. Specify a freestyle area where users can arrange tasks freely (like a canvas).
  6. Describe the statistics page: charts for task completion rates, overdue tasks, team workload.
  7. Ensure responsive design and intuitive UX. Include wireframe descriptions or mockup ideas.

Output format A specification document with sections: Overview, Data Model, Feature Descriptions, UI Layout, Interactions, Tech Recommendations, Acceptance Criteria. Use bullet points and subheadings.

Guardrails

  • Do not write actual code; focus on design and requirements.
  • Assume the app needs to be scalable; consider performance of real-time updates.
  • If technical decisions are missing, note assumptions (e.g., default to REST API).

Example {{core_features}}: board with tags, assignments, color coding, status; weekly calendar with left/right arrows; freestyle area; statistics. {{tech_stack}}: React, Node.js, MongoDB. {{user_roles}}: admin, member.