Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    Brownfield Reverse Specifier

    1

    Reverse-engineers undocumented codebases into structured 7-file specification suites and task baselines.

    $2

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Brownfield Reverse Specifier

    Brownfield Reverse Specifier

    Example session with this skill installed

    Onboard this Node/Express repo. It has a Postgres DB and React frontend. Reverse-engineer the current state into the specs/ folder and create the TASKS.md baseline.

    • Read your context and instructions
    • Compiled the brownfield reverse specifier

    I have inspected the repository manifests, directory structure, and source code. The project uses Express for the API, Sequelize for Postgres migrations, and a React/Tailwind frontend. I have reverse-engineered the existing capabilities into the 7-file specification suite and generated a baseline task list.

    Project Baseline (specs/TASKS.md)

    PhaseTask IDDescriptionStatus
    Phase 0ARCH-BSL-1Express Server Core & Middleware[✓]
    Phase 0DB-TBL-1Users & Authentication Schema[✓]
    Phase 0SEC-AUTH-1JWT-based Auth Strategy[✓]
    Phase 0UI-CMP-1React Dashboard & Sidebar[✓]
    Debt-1SEC-GAP-1Implement rate limiting on /api/login[ ]
    Debt-1TST-GAP-1Add integration tests for Sequelize models[ ]
    Debt-1ARCH-HLT-1Implement /health health-check endpoint[ ]

    Onboarding Summary

    The following files were created in the specs/ directory:

    • 0-product-requirements-document.md: Mapped existing features to PRD-US-*.
    • 1-architecture.md: Documented the Express/Node service layer and RAG setup.
    • 2-database-schema.md: Extracted User, Session, and Post models.
    • 3-security-design.md: Defined current CORS and JWT middleware logic.
    • 4-user-interface-design.md: Documented Tailwind theme and component library.
    • 5-testing-plan.md: Identified existing Jest suites and current gaps.
    • 6-deployment-config.md: Parsed Dockerfile and environment requirements.

    Next steps

    1. Review specs/3-security-design.md for identified technical debt in the auth flow.
    2. Run change-and-triage-lead to begin implementing the Debt-1 hardening tasks.
    3. Validate the ARCH-API-* tags against your API documentation.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Brownfield codebases often lack the documentation required for reliable agentic development. This skill solves the "cold start" problem for legacy repositories by reverse-engineering existing logic, schemas, and architecture into a structured specification format. It allows you to onboard undocumented code into a spec-driven workflow without manual auditing.

    What it does

    • Architectural Discovery maps existing directory structures, route controllers, and service layers into a formal architecture document.
    • Schema Extraction parses migration files and models to document the current database state and entity relationships.
    • UI/UX Auditing identifies Tailwind configurations, component patterns, and design tokens used in the current frontend.
    • Security Mapping documents existing auth middleware, RBAC rules, and environment variable requirements.
    • Technical Debt Logging flags security vulnerabilities or missing test coverage discovered during the inspection.

    How it works

    1. Inspection of project manifests, directory trees, and configuration files to identify the tech stack.
    2. Analysis of controllers, middleware, and database schemas to reconstruct the product logic.
    3. Clarification of any ambiguous modules with focused questions and recommended defaults.
    4. Generation of the canonical 7-file specs/ folder and a TASKS.md baseline reflecting the current state.

    Frameworks & tools

    Works with any repository containing standard manifests like package.json, pyproject.toml, Dockerfile, or .env.example. It parses SQL migrations, UI components, and API route definitions.

    Why this beats prompting it yourself

    Writing a complete specification for an existing project is tedious and prone to missing edge cases in auth or database constraints. This skill enforces a consistent tagging system (PRD-US-1, ARCH-API-1) across seven distinct files, ensuring the entire context is synchronized for downstream agent tasks.

    Use cases

    • Onboarding a legacy codebase into a new agent-led development workflow.
    • Documenting a project inherited from another team or contractor.
    • Auditing security and test gaps before starting a major refactor.
    • Standardizing documentation for multiple microservices into a unified format.

    Known limitations

    Does not modify application code, migrations, or tests. Relies on existing file visibility to infer logic; highly obfuscated code or missing manifests may reduce accuracy.

    Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Agents & Orchestration.

    Does not modify application code or fix bugs. Requires read access to manifests and schemas. Ambiguous logic requires user confirmation of recommended defaults.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before buying a skill.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 27 days ago

    Permissions

    Read Files
    Write Files
    Terminal / Shell
    Listed27 days ago

    What's inside

    Frequently Asked Questions

    This skill automates the 'cold start' phase of legacy development by transforming undocumented code into a structured, 7-file specification suite, providing immediate architectural clarity for both human developers and AI agents.

    The output is a standardized `specs/` folder containing PRD, Architecture, Database Schema, Security, UI/UX, and Technical Debt documents, plus a `TASKS.md` file for immediate action items.

    It is designed for any agentic workflow that follows a spec-driven development model and works across common stacks including Node.js, Python, and Docker-based environments.

    No, the skill operates in a strictly read-only capacity, analyzing your directory tree and code patterns to generate external documentation without altering your source code.

    The tool excels with standard manifests and clean architecture; however, highly obfuscated code or missing configuration files may limit its ability to map specific logic flows accurately.

    New in Agents & Orchestration