Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 10 additions & 0 deletions docs/assets/css/styles.css
Original file line number Diff line number Diff line change
Expand Up @@ -706,6 +706,16 @@ nav {
min-width: 200px;
}

.comparison-table a {
color: var(--accent-green);
text-decoration: none;
}

.comparison-table a:hover {
color: var(--accent-green-hover);
text-decoration: underline;
}

/* Quote */
.quote {
border-left: 4px solid var(--accent-green);
Expand Down
62 changes: 40 additions & 22 deletions docs/comparison.html
Original file line number Diff line number Diff line change
Expand Up @@ -37,73 +37,91 @@ <h1>Why Not Other Structured Development Tools?</h1>
<div class="container">
<h2>Comparison: Liatrio's Prompts vs. Other Structured Development Tools</h2>
<p class="section-intro">How do Liatrio's prompts compare to other structured development tools? Here's
a side-by-side look at the key differences.</p>
a side-by-side look at the key differences between Liatrio's prompts and three competitors.</p>

<div class="comparison-table-wrapper">
<table class="comparison-table">
<thead>
<tr>
<th>Feature</th>
<th>Liatrio's SDD Prompts</th>
<th>Kiro / SpecKit / Taskmaster</th>
<th>Kiro</th>
<th>SpecKit</th>
<th>Taskmaster</th>
</tr>
</thead>
<tbody>
<tr>
<td><strong>Setup & Installation</strong></td>
<td>✅ Just 4 markdown files—no installation</td>
<td>❌ Kiro: Requires downloading IDE app. SpecKit: Requires installation and
configuration. Taskmaster: Requires installation and setup.</td>
<td><a href="https://github.com/liatrio-labs/spec-driven-workflow">Four markdown files added to prompts</a></td>
<td><a href="https://kiro.dev/downloads/">Requires downloading IDE or cli</a></td>
<td><a href="https://github.com/github/spec-kit">Install SpecKit cli tooling</a></td>
<td><a href="https://docs.task-master.dev/getting-started/quick-start/installation#option-1-mcp-recommended">MCP installation</a></td>
</tr>
<tr>
<td><strong>Editor/IDE Dependency</strong></td>
<td>✅ Works with any editor (VS Code, Cursor, etc.)</td>
<td>❌ Kiro: Requires switching to Kiro IDE. SpecKit/Taskmaster: Work within existing
editors but require specific setup.</td>
<td>❌ Requires switching to Kiro IDE ( can import VS Code settings) </td>
<td>✅ Works within existing editor (VS Code, Cursor, etc.)</td>
<td>⚠️ Work within existing editors but require MCP setup</td>
</tr>
<tr>
<td><strong>AI Assistant Compatibility</strong></td>
<td>✅ Works with any AI assistant (Claude, GPT, Gemini, etc.)</td>
<td>❌ Kiro: Built-in AI. SpecKit: Works with GitHub Copilot, Claude Code, Gemini CLI.
Taskmaster: Works with Claude, Cursor, etc.</td>
<td>⚠️ Built-in agent but works with many models</td>
<td>✅ Works with any AI assistant (Claude, GPT, Gemini, etc.)</td>
<td>✅ Works with any AI assistant (Claude, GPT, Gemini, etc.)</td>
</tr>
<tr>
<td><strong>Learning Curve</strong></td>
<td>✅ Just read markdown prompts—no new concepts</td>
<td>❌ Kiro: Learn new IDE. SpecKit: Learn command system (`/speckit.specify`,
`/speckit.plan`, etc.). Taskmaster: Learn task management system.</td>
<td>⚠️ Simple tooling but chage to development process</td>
<td>⚠️ Learn new IDE but low learning curve because based on VS Code </td>
<td>⚠️ Learn command system (`/speckit.specify`,
`/speckit.plan`, etc.)</td>
<td>❌ Learn task management system</td>
</tr>
<tr>
<td><strong>Transparency</strong></td>
<td>✅ Every prompt is readable markdown—no black boxes</td>
<td>❌ Tool logic is hidden in codebases. Can't easily see or modify how they work.</td>
<td>❌ Tool logic is hidden in codebases. Can't easily see or modify how they work</td>
<td>✅ Available on GitHub, markdown is readable and editable</td>
<td>⚠️ Open source but logic hidden in JS packages</td>
</tr>
<tr>
<td><strong>Flexibility</strong></td>
<td>✅ Edit prompts to fit your project/style/company guidelines</td>
<td>❌ Limited customization. Must work within tool's structure and constraints.</td>
<td>❌ Limited customization. Must work within tool's structure and constraints</td>
<td>✅ Can freely edit markdorn files based on project/style/company guidelines</td>
<td>⚠️ Task templates and AI prompts can be configured</td>
</tr>
<tr>
<td><strong>File Structure</strong></td>
<td>✅ Simple <code>docs/specs/</code> that doesn't pollute repo</td>
<td>❌ Kiro: IDE-specific files. SpecKit: Creates <code>.specify/</code> directory
structure. Taskmaster: Task management files.</td>
<td>Repository specific <code>docs/specs/</code> folder structure</td>
<td>IDE-specific files stored at <code>.kiro</code></td>
<td>Creates <code>.specify/</code> directory
structure.</td>
<td>Task management files stored in <code>.taskmaster/</code></td>
</tr>
<tr>
<td><strong>Workflow Integration</strong></td>
<td>✅ Fits into your existing workflow—no context switching</td>
<td>❌ Kiro: Requires switching IDEs. SpecKit: Requires using specific commands.
Taskmaster: Requires managing tasks through tool.</td>
<td>❌ Requires switching IDEs</td>
<td>✅ Fits into your existing workflow—no context switching</td>
<td>❌ Requires managing tasks through tool </td>
</tr>
<tr>
<td><strong>Speed</strong></td>
<td>✅ Complete feature in minutes (example: &lt;15 min)</td>
<td>⚠️ Varies by tool, but requires learning and setup overhead</td>
<td>⚠️ Varies</td>
<td>⚠️ Varies</td>
<td>⚠️ Varies</td>
</tr>
<tr>
<td><strong>Cost</strong></td>
<td>✅ Free—just markdown files</td>
<td>✅ All are open source, but require time investment to learn</td>
<td>✅ Free markdown files</td>
<td>❌ Requires license</td>
<td>✅ Open source</td>
<td>⚠️ Open source but commercial use has limitatons</td>
</tr>
</tbody>
</table>
Expand Down