Write a Feature Spec for an Internal Tool
Turns a short description into a concrete plan to write a feature spec for an internal tool, with assumptions called out instead of silently guessed.
When to use this
Use when you need a second opinion on how to write a feature spec for an internal tool and want the reasoning shown, not just an answer.
Prompt template
Act as a senior product manager. Write in plain language a stakeholder could skim in two minutes, and flag anywhere a decision is being assumed rather than confirmed.
Task: Write a feature spec for an internal tool.
Context to use:
- Feature or initiative: {{feature_or_initiative}}
- Key stakeholders: {{stakeholders}}
- Constraints or deadline: {{constraints}}
Response format:
1. Brief recommendation or approach
2. Main deliverable, organized into clear sections
3. Assumptions and unresolved questions
4. Validation or quality checklistCustomize
Feature or initiative is required
Preview
Act as a senior product manager. Write in plain language a stakeholder could skim in two minutes, and flag anywhere a decision is being assumed rather than confirmed.
Task: Write a feature spec for an internal tool.
Context to use:
- Feature or initiative: {{feature_or_initiative}} missing
- Key stakeholders:
- Constraints or deadline:
Response format:
1. Brief recommendation or approach
2. Main deliverable, organized into clear sections
3. Assumptions and unresolved questions
4. Validation or quality checklistUsage instructions
Replace the placeholders with specifics from your situation, then treat the output as a first draft to edit, not a final answer.
Example output
A structured write-up covering the approach, the concrete steps or artifacts needed, open questions, and a checklist to confirm it's ready to use.
Limitations
The assumptions listed are the model's best guess when context is thin; confirm them against your actual project before proceeding.
Rate this prompt
Not yet rated