lucasbiason/legacy-specifier
skills/workflow/legacy-specifier/SKILL.md
Extrai especificações de um sistema legado (código existente) quando não há documentação adequada.
$ install --global
skillsauthnpx skillsauth add lucasbiason/cursor-multiagent-system legacy-specifierInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 6, 2026, 8:26 AM34.4s1 file scanned
SKILL.md
- name:
- legacy-specifier
- description:
- Extrai especificações de um sistema legado (código existente) quando não há documentação adequada.
- triggers:
- [legacy, reverse engineer, extract spec, existing code]
Legacy Specifier
Purpose
Reverse-engineer specifications from an existing system:
- Identify behaviors from code, routes, UI, tests
- Extract APIs and contracts
- Infer business rules ONLY when strongly evidenced
- Mark uncertainties explicitly
This skill prioritizes accuracy over completeness.
When to Use
- User asks to extract specs from repo/code
- Plan Lead routes "existing codebase" input to this skill
Inputs
- Repository code, existing docs (if any)
- API schemas (OpenAPI), test suites, UI flows (routes/pages)
Outputs
- spec/00-context/system-context.md (update)
- spec/20-design/api-contracts.md
- spec/30-features/<FEATURE-ID>/{spec.md, acceptance.md, test-plan.md}
- spec/99-meta/open-questions.md
Rules (non-negotiable)
- Never guess business intent. If unclear →
UNKNOWN+ Open Question. - Prefer evidence sources in this order: tests > docs > code paths > UI > comments.
- Separate: Observed behavior (fact) vs Intended behavior (hypothesis, mark as such).
- Track "contract surface" carefully: public APIs, payloads, status codes; UI visible behaviors; integrations.
Process
Step 0 — System Map
Produce a map: Components (services, frontend, jobs), Entry points (routes, commands), Data stores, Integrations.
Step 1 — Contract Extraction
For each entry point: Inputs, Outputs, Errors, Auth requirements (if observed), Side effects.
Step 2 — Behavior Extraction
Identify: Happy path, Validation, Authorization, Idempotency/retries (if present), Pagination/sorting rules, Data boundaries.
Step 3 — Feature Grouping
Group endpoints + UI flows into feature candidates. Assign FEATURE-001, FEATURE-002…
Step 4 — Spec Drafting
For each feature: Write spec.md (observed behavior), acceptance.md (provisional if needed), test-plan.md (existing tests + missing ones).
Step 5 — Unknowns + Risks
List open questions: Intent unclear, Inconsistent behavior across services, Missing tests for critical paths.
Feature Spec Template (legacy)
FEATURE-XXX — <name>. Status: LEGACY-DERIVED. Confidence: HIGH | MEDIUM | LOW. Evidence (files/tests/docs). Observed Behavior. Inputs/Outputs. Business Rules (Observed). Edge Cases. Known Gaps/Uncertainties. Acceptance (Provisional if needed) with GWT scenarios.
Related Skills
lucasbiason/test-runner
testing
VerifiedTrustedCommunity
Execução e análise de testes automatizados
2SKILL.mdUpdated May 6, 2026
lucasbiason/study-summary-rich
development
VerifiedTrustedCommunity
Gera resumos didáticos extensos e estruturados de aulas/cursos para cards do Notion. Use ao resumir aulas, apostilas, transcrições ou materiais de estudo para incluir no corpo do card (não apenas no campo Descrição), com flashcards, exemplos de código, diagramas Mermaid, mapa conceitual e perguntas de reforço.
2SKILL.mdUpdated May 6, 2026
lucasbiason/spec-normalizer
development
VerifiedTrustedCommunity
Padroniza documentação existente no formato canônico Spec-Driven. Remove duplicação e melhora rastreabilidade.
2SKILL.mdUpdated May 6, 2026
lucasbiason/spec-driven-core
development
VerifiedTrustedCommunity
Processo universal e repetível para criar especificações a partir de qualquer input (texto, docs, código). Usado em Plan mode.
2SKILL.mdUpdated May 6, 2026