init-prompt

Parse task descriptions into goal, constraints, and acceptance criteria.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/FScoward/senju --skill init-prompt
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: init-prompt
Source: https://github.com/FScoward/senju/tree/main/skills/init-prompt
Command: npx skills add https://github.com/FScoward/senju --skill init-prompt

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

It streamlines the process of clarifying and structuring initial task instructions, reducing ambiguity and miscommunication.

Core Features & Use Cases

  • Structured Prompt Creation: Transforms vague task descriptions into a clear Goal, Constraints, and Acceptance Criteria format.
  • Application Scenarios: Useful for project planning, task breakdowns, and ensuring alignment before execution in software and operational tasks.
  • Use Case: When given a broad or imprecise request like "add a search feature," it generates a detailed structured prompt to guide implementation and testing.

Quick Start

Provide a vague task description such as "add filtering to search results," and the skill will generate a three-part structured prompt defining the goal, constraints, and success criteria.

Frequently Asked Questions about init-prompt

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I structure vague task descriptions for software development?

To structure vague task descriptions, parse the initial request to generate a concise set of goals, constraints, and acceptance criteria, reducing ambiguity and ensuring clear communication before proceeding with execution.

What is the best way to define acceptance criteria for feature planning?

The best way to define acceptance criteria for feature planning is by analyzing the initial task description for key objectives and limitations, transforming broad requests into a structured three-part prompt.

Can I use prompt engineering to fix miscommunication in project planning?

Yes, you can use prompt engineering to fix miscommunication in project planning by clarifying initial task directives, applying structured formats to define specific goals and boundaries before execution.

How do I turn an imprecise request into a high-quality prompt for bug fixing?

To turn an imprecise request into a high-quality prompt for bug fixing, analyze the input for completion standards and limitations, producing a structured prompt that guides implementation and testing.

Do I need specific dependencies to clarify workflow requirements?

No specific dependencies are required to clarify workflow requirements, as the task structuring process operates independently to parse initial task descriptions and generate structured goal and constraint outputs.