myspec.dev valid

MySpec (myspec.dev) - Spec-Driven Development Platform & MCP Server

MySpec is the AI Senior Architect for Spec-Driven Development (SDD). It interviews you with focused multiple-choice questions, then writes implementation-ready specification bundles file by file - `constitution.md`, `requirements.md`, `solution.md`, `tasks.md` (plus `proposal.md` for brownfield changes) - with a collect → generate → review gate on every file, and streams them into Cursor, Claude Code, Claude Desktop, and any MCP client via `@myspec/mcp-server`.

Visit publisher ↗

Authority: 45 reach 0 · trust 5 · quality 25 · freshness 15
Tier: listed
llms.txt: http://myspec.dev/llms.txt
llms-full.txt: http://myspec.dev/llms-full.txt
Sections: 3
Links: 27
Size: 7589 bytes
Country: — Publisher location unknown; CDN address excluded
Country evidence: No published address evidence collected yet
For agents: Documentation: developer or product docs worth reading, nothing to call
First seen: 2026-10-27T09:57:08.114Z
Last checked: 2026-10-27T09:57:10.479Z
Badge

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-27T09:57:08.118Z. Cached copy · Source on myspec.dev

# MySpec (myspec.dev) - Spec-Driven Development Platform & MCP Server

> MySpec is the AI Senior Architect for Spec-Driven Development (SDD). It interviews you with focused multiple-choice questions, then writes implementation-ready specification bundles file by file - `constitution.md`, `requirements.md`, `solution.md`, `tasks.md` (plus `proposal.md` for brownfield changes) - with a collect → generate → review gate on every file, and streams them into Cursor, Claude Code, Claude Desktop, and any MCP client via `@myspec/mcp-server`.

## Core Concepts & Philosophy

- **Spec-Driven Development (SDD)**: A software engineering methodology where structured, version-controlled specifications precede code generation to eliminate AI hallucinations, context window decay, and architectural drift.
- **The MySpec Spec Bundle** (written to `specs/<bundle>/`):
  - `constitution.md`: Project Vision, Core Principles, Technology / Architecture Constraints, Testing Approaches, Coding Standards, Security Constraints, Performance Targets, Integration Points.
  - `requirements.md`: User Roles, FR-xxx functional requirements with EARS+ acceptance criteria, NFR-xxx with measurable targets, Data and Integration requirements, requirement diagrams. Brownfield variant: a Requirements Delta coded AR- (add) / BR- (remove) / CR- (change).
  - `solution.md`: Technology stack, architecture (Mermaid flowchart + C4 diagrams), system modules, data model (Mermaid erDiagram), API design, security, deployment, success criteria, key decisions. Older bundles named this file `design.md`.
  - `tasks.md`: Milestones of sized (Small/Medium/Large) tasks with acceptance criteria, dependencies, requirement traceability, man-day estimates, a QA verification milestone, and a dependency graph.
  - `proposal.md` (brownfield): Why, What Changes, Technical Solution (library / flow / schema / API changes with Mermaid diagrams), Impact.
- **Three supported methodologies / four generate workflows**:
  - MySpec greenfield: interview → constitution → requirements → solution → tasks.
  - MySpec brownfield: interview (explores the codebase) → proposal → requirements delta → optional tasks.
  - Spec Kit greenfield (GitHub Spec Kit-compatible): interview → constitution (`specs/memory/constitution.md`) → specify (`specs/NNN-feature/spec.md`) → plan (`plan.md`) → tasks (`tasks.md`).
  - OpenSpec brownfield (OpenSpec CLI-compatible): explore → proposal → delta specs (`openspec/changes/<change-id>/specs/<capability>/spec.md`) → design (`design.md`) → tasks.
  - An Edit workflow refines existing files: reference files → describe changes → review diffs.
- **EARS / EARS+ Syntax**: Easy Approach to Requirements Syntax with 6 patterns (Ubiquitous, State-Driven WHILE, Event-Driven WHEN, Optional Feature WHERE, Unwanted Behaviour IF…THEN, Complex) and EARS+ acceptance-criteria patterns (WHEN/AND/THEN, WHILE, IF…THEN, IF…WHEN…THEN).

## Key Pages & Documentation

- [MySpec Docs](https://docs.myspec.dev/llms.txt): Offic
…

Related sites

Explore similar publishers →

Similar publisher descriptions and documentation. Similarity does not imply affiliation or equivalent capabilities.

Domain	Title	Category	Country	Authority	llms.txt	llms-full.txt
acai.sh	Acai.sh	documentation Developer tools	US	45	✓	✓
docuwriter.ai	DocuWriter.ai	interface AI and machine learning Developer tools +1 Read documentation Search content+1	—	57	✓	✓
apimatic.io	APIMatic	interface Developer tools AI agents and MCP Read documentation Call an API	US	48	✓
medo.dev	MeDo	documentation AI and machine learning Developer tools Read documentation	US	49	✓
moxiedocs.com	Moxie Docs	interface AI and machine learning Developer tools +2 Read documentation Support / contact	US	51	✓	✓
chatforest.com	ChatForest	documentation Data and analytics Developer tools +2 Read documentation Search content	US	52	✓
mentorcruise.com	MentorCruise	interface Recruiting and careers AI agents and MCP Read documentation Call an API+3	—	61	✓	✓
jamdesk.com	Jamdesk	documentation Developer tools Documentation and reference Read documentation	US	50	✓	✓

Machine-readable: GET /v1/resolve?q=myspec.dev · GET /v1/domain/myspec.dev · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Own or manage this website?

If you own or manage myspec.dev, you can update its listing and review file health, discovery activity and score history.

Manage this listing — optional

What verification unlocks

See how your site is discovered—and control what agents see.

See your website in the map
Review your indexed topics, nearby publishers sharing headings, measured listing exposure and map snapshots in a private report for your website.
Control what agents see
Edit your listing description, tags, public contact details and additional llms.txt paths. Publish your terms for automated access, attribution and pricing.
Make your profile eligible for search
A valid, listed, unblocked, verified profile can appear in our publisher sitemap and become eligible for search-engine visibility. Search engines decide what to index and rank.
Appear in our llms-full.txt
Eligible verified publishers are listed by name, with their file links and summaries, in the service overview agents can read.

Free. No account registration, backlink or payment required. Public discovery remains available without verification.

Verify your website—free

Preview the owner dashboard · All verification benefits

Let your coding agent verify it

If your coding agent is authorized to manage this website, paste these instructions into it.

Claim my listing on Agent Web Map for myspec.dev:
1. POST https://agentwebmap.com/v1/sites/myspec.dev/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://myspec.dev/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/myspec.dev/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/myspec.dev).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.