project-spec-creator

name	project-spec-creator
description	Helps users define project specifications through iterative questioning and generates comprehensive .md design documents.
compatibility	Works with local workspaces.
license	MIT
resources	["templates/standards.md"]
metadata	{"author":"thiagoevoa","triggers":{"keywords":["create:spec","create:project-spec","create:sdd"]}}

Project Specification Creator

Use this skill to help users translate vague project ideas into robust, actionable Software Design Documents (SDD). It follows a structured, iterative discovery process to ensure all requirements, edge cases, and technical constraints are well-defined before any code is written.

Objectives

• Iterative Discovery: Use a clarifying dialogue to flush out project details, ambiguities, and edge cases.
• Structured Artifacts: Generate a comprehensive set of markdown documents (Constitution, Functional Spec, Technical Plan, Task List).
• Consistency: Ensure all specs align with core project principles and architectural standards.
• Actionability: Produce a task list that can be directly used by implementation agents.

Instructions

1. Initial Intake

When a user provides a project idea:

• Acknowledge the idea.
• Search for an existing CONSTITUTION.md or similar principles file in the workspace to align the new project with existing standards.

2. Iterative Discovery Phase (Clarification) - MANDATORY

Do NOT generate the final specs immediately. This is a blocking step.

1. Analyze for Ambiguity: Identify vague terms, missing workflows, or undefined constraints.
2. Ask Clarifying Questions: Present a concise list of questions to the user. You MUST wait for a response before moving to artifact generation. Focus on:
   • Functional: User roles, primary actions, and desired value.
   • Edge Cases: "What happens if...?" scenarios (invalid input, network loss, empty states).
   • Technical Constraints: Specific libraries, target platforms, or performance requirements.
3. Approval Gate: Only transition to "Artifact Generation" once the user's responses provide sufficient detail to satisfy the standards in templates/standards.md.

3. Artifact Generation

Once the user's answers provide sufficient clarity:

1. Draft Artifacts: Generate the following files following the structures in templates/standards.md:
   • spec/CONSTITUTION.md (Project principles and tech standards).
   • spec/FUNCTIONAL_SPEC.md (User stories and acceptance criteria).
   • spec/TECHNICAL_PLAN.md (Architecture, data model, and research).
   • spec/TASKS.md (Atomic, traceable implementation steps).
2. Review: Present the generated specs to the user for final approval.

Workflow Example

1. User: "I want to build a simple task manager."
2. Agent: "That sounds great! To make the specification robust, I have a few questions:
   • Should tasks support priorities or categories?
   • Is this a local-only app or does it need sync/auth?
   • How should it handle tasks that are past their due date?"
3. User: [Answers questions]
4. Agent: [Asks follow-up if needed, then generates the .md files in the spec/ directory]

Parameters

• output_dir (string, optional): Directory where the specs should be saved. Defaults to spec/.