SponsoredDeveloper Deals

Markdown User Story & Acceptance Criteria Formatter

Standardize agile requirements with industry-standard Given-When-Then Gherkin acceptance criteria. Ready to copy into Jira, GitHub Issues, and Linear.

Agile User Stories (2)

Priority

Story Points (Fibonacci)

As a:

I want:

So that:

Acceptance Criteria (3)

Scenario 1

Given:

When:

Then:

Scenario 2

Given:

When:

Then:

Scenario 3

Given:

When:

Then:

Implementation Notes & Architecture Constraints

Priority

Story Points (Fibonacci)

As a:

I want:

So that:

Acceptance Criteria (2)

Scenario 1

Given:

When:

Then:

Scenario 2

Given:

When:

Then:

Implementation Notes & Architecture Constraints

Agile Markdown Output (.md)2 stories formatted

## [AUTH-101] OAuth2 Social Sign-In with GitHub
**Priority**: `High` | **Points**: `5`

### User Story
> **As a** developer visiting MarkdownKite
> **I want** to sign in with my existing GitHub credentials
> **So that** I can sync my custom Markdown templates across all my workstations without creating a new password

### Acceptance Criteria (Gherkin)

#### Scenario 1
- **Given** an unauthenticated user on the login screen
- **When** the user clicks 'Continue with GitHub'
- **Then** they are redirected to GitHub's OAuth authorization page with read:user scope

#### Scenario 2
- **Given** the user grants authorization on GitHub
- **When** GitHub redirects back with a valid authorization code
- **Then** an active session is established and the user is redirected to their recent documents dashboard

#### Scenario 3
- **Given** the user denies GitHub OAuth permissions
- **When** the callback returns with an access_denied error
- **Then** a clear non-blocking error message is displayed with fallback login options

### Implementation Notes
Requires setting up GITHUB_CLIENT_ID and GITHUB_CLIENT_SECRET environment variables in Next.js.

---

## [EXPORT-204] Client-Side Markdown to Clean HTML Export
**Priority**: `Medium` | **Points**: `3`

### User Story
> **As a** technical documentation author
> **I want** to export my rendered Markdown directly as sanitized HTML with inline CSS styles
> **So that** I can embed release notes directly into newsletters or legacy CMS portals without external stylesheets

### Acceptance Criteria (Gherkin)

#### Scenario 1
- **Given** a completed Markdown document in the editor
- **When** the user clicks 'Export Inline HTML'
- **Then** an HTML file is generated in-memory with scoped Tailwind typography styles included

#### Scenario 2
- **Given** the user selects clipboard copy instead of file download
- **When** they click 'Copy HTML'
- **Then** the sanitized HTML string is written to navigator.clipboard with a 2-second confirmation toast

### Implementation Notes
Ensure all script tags and iframe vectors are stripped using DOMPurify before export.

---

SponsoredDeveloper Deals

Complete Guide & Overview

Markdown User Story & Acceptance Criteria Formatter

Format agile user stories and Gherkin Given-When-Then acceptance criteria tables for Jira, GitHub Projects, and Linear. Ensures clear engineering contracts and testable requirements.

How to Use the Markdown User Story & Acceptance Criteria Formatter

Input Content

Paste or compose your markdown or source data into the input editor.

Customize Settings

Select formatting options, syntax modes, or display options.

Copy or Download

Copy the processed output to your clipboard or download the generated file.

Key Features & Capabilities

Gherkin Given-When-Then Format: Automatically converts agile scenarios into clear behavior-driven development (BDD) specifications.

Story Points & Priority: Estimate work with Fibonacci points and prioritize with standard P0-P3 urgency badges.

Jira & Linear Ready: Generates standard GitHub Flavored Markdown that copies seamlessly into tickets.

Strict Client-Side Privacy: Your proprietary product roadmaps and customer requirements never touch a server.

Frequently Asked Questions

Why should I write acceptance criteria in Given-When-Then format?

Given-When-Then (Gherkin syntax) removes ambiguity by clearly stating the initial condition (Given), the user or system trigger (When), and the expected verifiable outcome (Then). It serves as an unshakeable contract between product and QA.

Does this Markdown format work with Jira and Linear?

Yes! Modern Jira Cloud and Linear both feature first-class Markdown parsers. Pasting this generated Markdown preserves quotes, headings, bullet lists, and code blocks cleanly.

Workflow Continuity