# Reported issues for SpecLeft

Pod holds 6 of 6 problems reported by people outside the maintainer team. Issues filed by the project's own owners, members and collaborators are excluded entirely — a maintainer's release checklist is not a warning to a prospective user.

Back to [SpecLeft](/mcp/specleft).

## Most discussed

### Documentation: language adapters guide (docs/language-adapters-guide.md)

## Summary

Add `docs/language-adapters-guide.md` — a step-by-step guide for adding new language support (grammars, miners, framework detection) to the discovery pipeline.

**Depends on:** #124, #125, #126

## Content

The guide has been drafted and committed to the repo. It covers:

1. Registering a new `SupportedLanguage` enum member
2. Adding the tree-sitter grammar package and loader
3. Extending `FrameworkDetector` for the new language
4. Creating miners (test functions, API routes) with `M

[Read the thread](https://github.com/SpecLeft/specleft/issues/138) · 2026-03-05 · open · outside contributor · 0 comments

### SpecLeft Skill

## Skill File — `.specleft/SKILL.md`

Generated by `specleft init`. Contains the full CLI reference that agents read once from disk. This will replace MCP tool declarations with a single file read.

**Target size:** ~800 tokens

**Structure:**

```markdown
# SpecLeft CLI Reference

## Workflow
1. specleft next → pick scenario
2. Implement test logic
3. specleft features validate → verify specs
4. pytest → run tests
5. Repeat

## Safety
- Always --dry-run before writing
- Never --force without us

[Read the thread](https://github.com/SpecLeft/specleft/issues/95) · 2026-02-15 · closed · outside contributor · 3 comments

### CLI Output Optimisation for Agent Context Efficiency

## Problem

Every CLI response enters the agent's context window and persists for the conversation. In a typical 12-scenario session with ~36 SpecLeft CLI calls, unoptimised responses accumulate ~10,800 tokens of JSON output — more than double the MCP declaration overhead. CLI response size is the largest controllable token cost in SpecLeft's footprint.

## Goal

Make SpecLeft the most context-efficient developer tool for AI coding agents. Target: **49% total session token reduction** compared t

[Read the thread](https://github.com/SpecLeft/specleft/issues/94) · 2026-02-15 · closed · outside contributor · 1 comment

### MCP Security and Risk management

## Security — v0.3.0 Scope

### Attack surface overview

The 3+1 MCP design has a smaller attack surface than a full-tool MCP server (one write operation instead of nine), but three vectors require mitigation before release.

```
Attack surfaces:
├── Skill file injection       ← Agent reads tampered instructions from disk
├── Init write safety          ← Symlinks or overwrites during project setup
├── CLI argument injection     ← Shell metacharacters in agent-supplied values
├── Contract spoofin

[Read the thread](https://github.com/SpecLeft/specleft/issues/91) · 2026-02-14 · closed · outside contributor · 2 comments

### [Feature] Publish SpecLeft to MCP Registry

## Summary

Publish SpecLeft's MCP server to the official Anthropic MCP Registry and automate future releases via CI/CD. This enables one-click installation in Claude Desktop and automatic discovery by MCP-compatible agents.

**Target release:** v0.3.0 (after MCP server implementation)

## Depends On

- #76 — MCP Server Implementation (must be merged first)

## Tasks
### 1. End-to-End Testing Flow

Verify the SpecLeft MCP server works as a real installed package over stdio transport — catching d

[Read the thread](https://github.com/SpecLeft/specleft/issues/77) · 2026-02-05 · closed · outside contributor · 3 comments

### Add MCP Server for Agent Discovery

SpecLeft MCP Server — Design Specification (v0.3)

## Goal

Add a new SpecLeft feature to accommodate MCP server for optimised agent utilisation and discovery.

## Acceptance criteria
- [ ] an MCP server is created with 3 resources and 1 tool
- [ ] the MCP specleft feature (feature-id: 'feature-mcp-server', priority: high) has been added in to `features/` with end-to-end scenarios to cover the resources and tool calls. 
- [ ] unit, integration, security and token usage test coverage
- [ ] Entry 

[Read the thread](https://github.com/SpecLeft/specleft/issues/76) · 2026-02-05 · closed · outside contributor · 2 comments

## Most recent

The remaining reports are on [the project's issue tracker](https://github.com/SpecLeft/specleft/issues).