Kickoff Prompt

KPKickoff Prompt26 included sections - 51/100 quality score

Prompt sections

Every section is optional.

Included

Skipped

INCLUDE

Project name

Template

Step 1 of 26 · Agent role4%

Current section

Agent role

Define the neutral role, working style and decision rules the coding agent should follow. This keeps the prompt model-neutral while setting expectations for how work should be approached.

INCLUDE

Role

Empty values render as not specified.

Working style

Empty values render as not specified.

AI assist

Bring your own API key. It is used only for the current request and never added to the prompt.

Prompt quality

Deterministic score, no AI call required.

51/100

Needs detail23 unspecified - 0 skipped

Strengths

Objective section contains usable direction.
Acceptance criteria are present for verification.
Verification commands are included.

Weaknesses

23 included fields still render as "not specified".
Security requirements are not specific yet.

Missing fields

Project context: Context
Target users: Use cases
Business goal: Business goal
Business goal: KPIs
Project status: Status
Project status: Existing assets
API: API contracts
Observability: Signals
Observability: Tools
Testing and QA: Test strategy
Testing and QA: QA notes
Security: Security requirements

Suggestions

Fill the highest-impact missing fields: objective, features, acceptance criteria and verification commands.
Add the minimum signals worth observing after launch.

Live preview

Exports include only INCLUDE sections.

Export only INCLUDE sections

# Kickoff Prompt

## Agent role

### Role
Act as a senior full-stack software engineer who ships production-ready, well-tested code.

### Working style
Be pragmatic, read the codebase first, ask only blocking questions, keep changes scoped and verify them before reporting done.

## Project objective

### Objective
Build a responsive web application where users can sign up, manage their data and complete the core workflow end to end.

### Success outcome
A logged-in user can complete the main task without help; the app is deployable and passes lint, typecheck and build.

## Project context

### Domain
Web application (B2B/B2C SaaS or internal tool)

### Context
not specified

## Target users

### Users
End users and an admin who manages content and accounts

### Use cases
not specified

## Business goal

### Business goal
not specified

### KPIs
not specified

## Project status

### Status
not specified

### Existing assets
not specified

## Features

### Core features
Authentication, main entity CRUD, list view with search/filter, detail pages, settings.

### Out of scope
Billing, native mobile app and third-party integrations beyond auth.

## Frontend

### Frontend stack
Next.js, React, TypeScript, Tailwind CSS, shadcn/ui

### Frontend requirements
Responsive, accessible, with clear loading/empty/error states.

## Backend

### Backend stack
Next.js Route Handlers, TypeScript

### Backend requirements
Validate inputs server-side, return typed responses, handle errors gracefully.

## Database

### Database stack
PostgreSQL

### Data model
Users and the main entity with created/updated timestamps.

## API

### API style
REST with typed request/response contracts

### API contracts
not specified

## Authentication and permissions

### Authentication method
Email/password with sessions

### Permissions
Roles: admin and member.

## Server, Docker and deployment

### Runtime and server
Node.js, Docker, Docker Compose

### Deployment
Single Docker image; deployable to Vercel or any container host.

## Observability

### Signals
not specified

### Tools
not specified

## Testing and QA

### Test strategy
not specified

### QA notes
not specified

## Security

### Security requirements
not specified

### Sensitive data
not specified

## Performance

### Targets
not specified

### Optimization priorities
not specified

## UX/UI and design system

### Design system
not specified

### UX/UI guidelines
not specified

## Constraints

### Constraints
not specified

## Deliverables

### Deliverables
not specified

## Acceptance criteria

### Criteria
Users can complete the main workflow; skipped sections are excluded; build, lint and tests pass.

## Verification commands

### Commands
npm run lint
npm run typecheck
npm run build

## Output format

### Output format
not specified

## Assumptions

### Assumptions
not specified

## Open questions

### Questions
not specified

## Operating instructions

### Instructions
not specified