Coding
PromptBeginner5 minmarkdown
Markdown Converter
Agent skill for markdown-converter
51
A lightweight task specification methodology using 4 documents:
Loading actions...
A lightweight task specification methodology using 4 documents:
Ask clarifying questions if the description is vague:
Generate in tasks/{task-name}/ or project root, following the exact structure below:
# {Task Name}
## Background
{Why does this task exist? What problem are we solving?}
## Goals
- {Goal 1}
- {Goal 2}
## Scope
### In Scope
- {What's included}
### Out of Scope
- {What's NOT included - be explicit}
## Dependencies
- [ ] {Dependency 1 - e.g., another task, external API, team decision}
## Resources
- {Link to related docs}
- {Link to external references}
# TODO
## Research
- [ ] {Research item 1}
- [ ] {Research item 2}
## Implementation
- [ ] {Task 1}
- [ ] {Task 2}
- [ ] {Task 3}
## Verification
- [ ] {Verification step}
---
## Acceptance Criteria
### Must Have
- [ ] {Criterion 1 - specific, measurable}
- [ ] {Criterion 2}
### Nice to Have
- [ ] {Optional criterion}
### Out of Scope
- {Explicitly NOT part of this task's acceptance}
# {Task Name} - Technical Document
## Summary
{One paragraph summary of the solution/outcome}
## Key Decisions
### Decision 1: {Title}
- **Options considered**: A, B, C
- **Chosen**: B
- **Rationale**: {Why B?}
## Technical Details
### Architecture / Data Flow
{Diagram using ASCII or describe the flow}
### Interfaces / Schema
```typescript
// Key interfaces if applicable
interface Example {
id: string;
name: string;
}
#### log.md
```markdown
# Development Log
## {YYYY-MM-DD}
### Done
- Task created
### In Progress
- {What's ongoing}
### Blocked
- {What's stuck and why}
### Notes
- {Discoveries, learnings, things to remember}
---
<!-- Copy the template above for each day -->
Show user what was created and ask if adjustments needed.