propose

Generate design, specs, and task files from a natural language change description.

1|Updated Mar 4, 2026
One-click install
npx skills add https://github.com/augentic/specify --skill propose-augentic
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: propose
Source: https://github.com/augentic/specify/tree/main/plugins/spec/skills/propose
Command: npx skills add https://github.com/augentic/specify --skill propose-augentic

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the initial phase of software development by automatically generating all necessary artifacts for a proposed change, from design to tasks, based on a user's description.

Core Features & Use Cases

  • Automated Artifact Generation: Creates design documents, specifications, and task lists in one go.
  • Structured Workflow: Ensures all required documentation is present before implementation begins.
  • Use Case: When you need to add a new feature like 'user profile editing', this Skill will generate the design.md, specs.md, and tasks.md files, ready for review and implementation.

Quick Start

Use the propose skill to generate artifacts for a new change described as 'add user authentication'.

Frequently Asked Questions about propose

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

FAQPage Schema
How do I generate design documents and specifications from a natural language description?

To generate design documents and specifications from a natural language description, use this Skill to orchestrate schema resolution and create a complete set of spec-driven development artifacts, including design, specifications, and tasks.

What is the best way to automate software development artifact creation for a new feature?

Automating software development artifact creation is best handled by generating a complete set of structured files like design, specifications, and tasks from your proposed change description, ensuring all required documentation is present before implementation begins.

How does spec-driven development workflow validate generated artifacts against rules?

Spec-driven development workflow validates generated artifacts by checking the created design, specifications, and tasks against defined rules and conventions, ensuring structured documentation accuracy before implementation.

Can I generate tasks and specs simultaneously from a proposed software change?

Yes, you can generate tasks and specs simultaneously from a proposed software change. The Skill processes your natural language input to instantly output design, specifications, and task lists in one go.

Do I need to manage dependencies manually when generating software specifications?

No, you do not need to manage dependencies manually when generating software specifications. The Skill automatically orchestrates dependency management and schema resolution during artifact creation.

What limitations exist when automating task list and design document generation?

Limitations of automating task list and design document generation include relying strictly on your natural language input clarity, as the Skill validates output against defined rules but requires accurate proposed change descriptions to function correctly.