Extracts specifications and requirements from existing codebases using code analysis.
npx skills add https://github.com/ArMaTeC/Redball --skill spec-miner-armatec
Please help me install this Agent Skill. Skill: spec-miner Source: https://github.com/ArMaTeC/Redball/tree/main/.devin/skills/spec-miner Command: npx skills add https://github.com/ArMaTeC/Redball --skill spec-miner-armatec
High-intent search queries and answers about installing and using this skill.
Reverse-engineer the specification by exploring entry points, routes, models, and auth patterns with Glob and Grep, then document observed behavior in EARS format. The output is a structured spec covering architecture, requirements, and open questions.
Trace route definitions and controllers using patterns like @Controller, router.get, or @app.route, then record endpoints, methods, request/response formats, and authentication requirements. Each observation includes its code location as evidence.
EARS (Easy Approach to Requirements Syntax) structures requirements as patterns like 'When [trigger], the system shall [action]' for events or 'While [state], the system shall [action]' for states. It produces unambiguous, testable requirement statements.
Yes. Observations must be grounded in actual code evidence with file locations, while inferences and uncertainties are flagged in a dedicated section. Assumptions without code evidence are explicitly prohibited.
It captures only what the code implements, not original intent or business rationale. Undocumented business rules, deployment context, and planned-but-unimplemented features must be flagged as questions for stakeholders.
ersinkocMaps codebase architecture and technology stack for targeted security analysis.
bitoviWrite tests before code and follow the red-green-refactor cycle.
AsiaOstrichAssess project health, architecture, and risks in existing codebases.
jmbeachAudits EARS-to-code mappings by comparing reconstructed EARS from code with original requirements.
