Run any Skill in Manus with one click

aiws-sdd-reverse-engineering

Stars2

Forks0

UpdatedJune 22, 2026 at 19:05

Recover a draft REASONS spec from an existing codebase that arrived without one (or whose spec drifted). Trigger: auditing code that lacks a current spec (reviewer/IT side).

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

grojof

grojof/ai-workspace-generator

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

File Explorer

2 files

SKILL.md

readonly

name	aiws-sdd-reverse-engineering
description	Recover a draft REASONS spec from an existing codebase that arrived without one (or whose spec drifted). Trigger: auditing code that lacks a current spec (reviewer/IT side).
license	Apache-2.0
metadata	{"author":"ai-workspace","version":"1.0"}

aiws-sdd-reverse-engineering — recover a spec from code (reviewer side)

When a project arrives without a spec (or its spec drifted), reconstruct a draft REASONS spec from the code so the sdd-audit-* skills have something to audit against. Reviewer/IT use; advanced.

How

Detect the profile from the layout (Profile A: pyproject.toml + layered src/; Profile B: index.html + js/).
Profile A: scan FastAPI routes, SQLAlchemy models, Pydantic schemas and use-cases to recover §2 Entities and §5 Operations. Profile B: scan index.html + JS modules for the operations and UI surfaces.
Write a versioned draft spec to {{paths.specs}}/<NNN>-<slug>.md with status: draft, a clear "reverse-engineered" banner, and TODO markers for sections the code can't reveal (business rationale, acceptance criteria, data-protection basis).

Hand-off

The draft must be confirmed by a human (sign-off → user-reviewed) before the audits run — the audits refuse drafts. Record the recovery in {{paths.changes}}/<change>/.

More from this repository

same repository

aiws-audit

grojof/ai-workspace-generator

Produce a prioritized, read-only audit of the workspace's health and coherence (code, docs, integrity, standards) as a dated report. Use periodically or after big changes to surface what to improve. Read-only — it reports and recommends, never fixes.

2026-06-232

aiws-configure-workspace

grojof/ai-workspace-generator

Configure or re-configure this AI workspace: analyze an existing repo (or set up a new one) and propose a workspace.config.yaml + skill set. Trigger: when the user wants to set up, configure, or re-detect the workspace.

2026-06-232

aiws-dependency-upgrade

grojof/ai-workspace-generator

Assess feasibility and security of version bumps/migrations before touching anything. Trigger: when asked to update dependencies, migrate, or resolve version conflicts.

2026-06-232

aiws-living-docs

grojof/ai-workspace-generator

Keep the living docs (project status) current so the AI always has fresh project context. Trigger: after finishing a task or when project state changed.

2026-06-232

aiws-sdd-apply

grojof/ai-workspace-generator

Implement the tasks in order, keeping the code aligned with the spec and design, checking each off as it lands. Use to execute an agreed plan — if reality diverges from the spec, stop and update the spec first.

2026-06-232

aiws-sdd-archive

grojof/ai-workspace-generator

Fold a verified change's delta into the stable specs and move its folder to the archive. Use only after verify passes: ADDED requirements are appended, MODIFIED replace, REMOVED delete; then the change is archived with its full history.

2026-06-232

name	aiws-sdd-reverse-engineering
description	Recover a draft REASONS spec from an existing codebase that arrived without one (or whose spec drifted). Trigger: auditing code that lacks a current spec (reviewer/IT side).
license	Apache-2.0
metadata	{"author":"ai-workspace","version":"1.0"}

aiws-sdd-reverse-engineering — recover a spec from code (reviewer side)

When a project arrives without a spec (or its spec drifted), reconstruct a draft REASONS spec from the code so the sdd-audit-* skills have something to audit against. Reviewer/IT use; advanced.

How

Detect the profile from the layout (Profile A: pyproject.toml + layered src/; Profile B: index.html + js/).
Profile A: scan FastAPI routes, SQLAlchemy models, Pydantic schemas and use-cases to recover §2 Entities and §5 Operations. Profile B: scan index.html + JS modules for the operations and UI surfaces.
Write a versioned draft spec to {{paths.specs}}/<NNN>-<slug>.md with status: draft, a clear "reverse-engineered" banner, and TODO markers for sections the code can't reveal (business rationale, acceptance criteria, data-protection basis).

Hand-off

The draft must be confirmed by a human (sign-off → user-reviewed) before the audits run — the audits refuse drafts. Record the recovery in {{paths.changes}}/<change>/.