gsd-to-autoforge-spec

You can convert GSD mapping outputs into an AutoForge app spec by running this skill after using /gsd:map-codebase. It reads your codebase mapping documents and automatically generates the required .autoforge/prompts/app_spec.txt file for project onboarding.

Migrating an existing codebase to AutoForge involves mapping your repository structure first, then converting those outputs into a structured app spec. This skill transforms your documented architecture and conventions into a ready-to-run spec for feature planning.

Generating an AutoForge app_spec.txt file requires the GSD mapping outputs from your .planning/codebase directory. Specifically, it reads STACK.md, ARCHITECTURE.md, STRUCTURE.md, CONVENTIONS.md, and INTEGRATIONS.md to populate the structured spec.

Yes, you can onboard an existing project to AutoForge without manual spec writing by applying this skill to your mapped codebase. It automatically translates your existing project documentation into a ready-to-run app_spec.txt for continued development.

Yes, you must run /gsd:map-codebase on your repository before generating an AutoForge app spec. This skill depends on the structured mapping outputs produced by that command to accurately populate the final specification file.

The primary limitation when converting GSD mappings to AutoForge specs is the strict dependency on prior codebase mapping outputs. Without complete and accurate GSD documents like STACK.md and ARCHITECTURE.md, the generated app_spec.txt will lack the necessary structure for feature planning.