goal-definition

Interview users to define goals and create handoff artifacts.

1|Updated Apr 11, 2026
One-click install
npx skills add https://github.com/himadajin/skills --skill goal-definition-himadajin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: goal-definition
Source: https://github.com/himadajin/skills/tree/main/skills/goal-definition
Command: npx skills add https://github.com/himadajin/skills --skill goal-definition-himadajin

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill solves the challenge of clarifying software development goals through structured, interview-driven artifact creation, ensuring a clear handoff before implementation.

Core Features & Use Cases

  • Interview-Driven Drafting: Utilizes conversational interviewing to define and draft software development goals.
  • Artifact Creation: Produces handoff artifacts including purpose.md, design.md, and companion files for comprehensive project handover.
  • Use Case: A developer seeking to scope a project would use this Skill to interview a client and create detailed artifacts, such as a purpose brief or a comprehensive design document.

Quick Start

Initialize the Skill to begin defining the software development goals. Engage in a dialogue with the Skill, providing details of the project objectives.

Frequently Asked Questions about goal-definition

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

FAQPage Schema
How do I define software development goals before starting implementation?

To define software development goals, you can use an interactive interview process to clarify project objectives and draft structured handoff artifacts such as purpose and design documents before coding begins.

Can I create handoff documents for a software project through an interactive interview?

Yes, you can create handoff documents through conversational interviewing, which guides you through scoping discussions to produce detailed artifacts like purpose.md and design.md for comprehensive project handover.

What is the best way to scope a software project for client handover?

The best way to scope a project for client handover is conducting an interview-driven dialogue to extract project details, ensuring the resulting purpose and design documents capture all necessary development objectives.

Do I need any specific frameworks to draft purpose and design documents for software development?

No specific frameworks are required to draft purpose and design documents, as the goal definition process relies entirely on user input during the conversational interview to generate the necessary project artifacts.

What artifacts are generated when defining software project goals through an interview?

The artifacts generated when defining software project goals include purpose.md, design.md, and companion files, which collectively form the comprehensive handoff documentation for the development team.