Schematic
blader/schematic
Reverse engineer a detailed product and technical specification document from a git branch's implementation.
A skill your agent uses when the user wants to turn an application, product, startup idea, SaaS, mobile app, web app, API, AI product, or internal tool into a production-ready Markdown specification…
Install App Spec Packager
$ npx skills add instructa/agent-skills --skill app-spec-packager -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install instructa/agent-skills app-spec-packager --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/instructa/agent-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/specs/app-spec-packager .claude/skills/app-spec-packager && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "app-spec-packager" agent skill from https://github.com/instructa/agent-skills/tree/main/skills/specs/app-spec-packager into .claude/skills/app-spec-packager/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "app-spec-packager", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/instructa/agent-skills/tree/main/skills/specs/app-spec-packagerType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add instructa/agent-skills --skill app-spec-packager -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install instructa/agent-skills app-spec-packager --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/instructa/agent-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/specs/app-spec-packager .agents/skills/app-spec-packager && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "app-spec-packager" agent skill from https://github.com/instructa/agent-skills/tree/main/skills/specs/app-spec-packager into .agents/skills/app-spec-packager/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "app-spec-packager", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add instructa/agent-skills --skill app-spec-packager -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install instructa/agent-skills app-spec-packager --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/instructa/agent-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/specs/app-spec-packager .cursor/skills/app-spec-packager && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "app-spec-packager" agent skill from https://github.com/instructa/agent-skills/tree/main/skills/specs/app-spec-packager into .cursor/skills/app-spec-packager/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "app-spec-packager", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/instructa/agent-skills.git --path skills/specs/app-spec-packager--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add instructa/agent-skills --skill app-spec-packager -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install instructa/agent-skills app-spec-packager --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/instructa/agent-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/specs/app-spec-packager .gemini/skills/app-spec-packager && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "app-spec-packager" agent skill from https://github.com/instructa/agent-skills/tree/main/skills/specs/app-spec-packager into .gemini/skills/app-spec-packager/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "app-spec-packager", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install instructa/agent-skills app-spec-packagerInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add instructa/agent-skills --skill app-spec-packager -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/instructa/agent-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/specs/app-spec-packager .github/skills/app-spec-packager && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "app-spec-packager" agent skill from https://github.com/instructa/agent-skills/tree/main/skills/specs/app-spec-packager into .github/skills/app-spec-packager/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "app-spec-packager", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add instructa/agent-skills --skill app-spec-packager -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install instructa/agent-skills app-spec-packager --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/instructa/agent-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/specs/app-spec-packager .opencode/skills/app-spec-packager && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "app-spec-packager" agent skill from https://github.com/instructa/agent-skills/tree/main/skills/specs/app-spec-packager into .opencode/skills/app-spec-packager/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "app-spec-packager", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
app-spec-packager- GitHub stars
- 139
- Token cost
- ~1.5k tokens
- SKILL.md length
- 571 words
- Files
- 9 (incl. scripts, references)
- Skills in repo
- 17
- Repo updated
- First seen
- Licence
- None found
At a glance
A skill your agent uses when the user wants to turn an application, product, startup idea, SaaS, mobile app, web app, API, AI product, or internal tool into a production-ready Markdown specification…
- Works in 7 steps: Capture the app intent, platform, target… → Ask only blocking questions. If the user… → Research current facts when the spec… → …
- The user wants to turn an application
- SKILL.md covers Default output, Core workflow, Reference loading and Writing rules, plus 4 more sections
- Runs Python scripts from its folder
What it does
App Spec Packager is an agent skill from instructa/agent-skills. Use this skill when the user wants to turn an application, product, startup idea, SaaS, mobile app, web app, API, AI product, or internal tool into a production-ready Markdown specification package for coding agents. Creates PRD/product spec, UX flows, design system brief, technical architecture, ADRs, AI/safety/privacy specs, API/data model, client/backend implementation specs, QA acceptance tests, release readiness, and executable task checklists. Do not use for simple one-off coding tasks unless the user asks…
Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 11 other files, including scripts and reference files (for example `README.md`, `agents/openai.yaml` and `references/document-blueprints.md`).
It sits in Product & Project Management, covering PRD writing, Architecture decision records and End-to-end testing. The repository describes itself as: A curated collection of agent-skills.
When your agent uses it
- The user wants to turn an application
- Internal tool into a production-ready Markdown specification package for coding agents
- Simple one-off coding tasks unless the user asks for a complete spec
- Project plan for coding agents
Example prompts
- “/app-spec-packager”
Requirements
- Python 3
Workflow steps
7 steps, taken from the first numbered list in SKILL.md.
- Capture the app intent, platform, target users, core workflows, data sensitivity, AI needs, monetization, integrations, and launch…
- Ask only blocking questions. If the user has already given enough context, proceed and mark assumptions explicitly.
- Research current facts when the spec depends on recent platform rules, SDK versions, app store rules, laws, payments, AI providers…
- Choose the relevant document set. Omit docs that are truly irrelevant, but keep privacy/security, QA, and tasks for production builds.
- Write requirements as precise, testable statements with stable IDs.
- Convert the spec into executable tasks for coding agents. Every task needs acceptance criteria and tests.
- Validate the package against references/validation-checklist.md before final output.
What it can do on your machine
Read from SKILL.md and the folder at commit d49c149. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships 1 file in scripts/ (Python), which the agent can run.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
App Spec Packager loads about 1.5k tokens when it runs, and up to ~9.3k if it reads all its reference files. Until then it costs about 154 tokens; SKILL.md has 571 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.
SKILL.md
Without a licence we can't republish the file, so here is its outline and opening line. It has 571 words (~1,537 tokens).
“Create complete, production-ready specification packages that coding agents can use to build applications without needing timelines, storypoints, budgets, or sprint planning.”
- name
- app-spec-packager
Files
SKILL.md and 8 other files (scripts, references) in skills/specs/app-spec-packager of instructa/agent-skills.
- SKILL.md
- README.md
- agents/openai.yaml
- references/document-blueprints.md
- references/platform-modules.md
- references/safety-privacy.md
- references/task-taxonomy.md
- references/validation-checklist.md
- scripts/create_spec_package.py
Open the folder on GitHubat commit d49c149
Compare with similar skills
App Spec Packager next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| App Spec Packager this skillinstructa/agent-skills | 139 | — | ~1.5k | Automated safety check: Pass | None | |
| Schematicblader/schematic | 240 | — | ~2.2k | Automated safety check: Pass | MIT | |
| Shep Workstreamsshep-ai/shep | 264 | — | ~2.5k | Automated safety check: Pass | MIT | |
| Sagawarpdotdev/common-skills | 608 | — | ~4.1k | Automated safety check: Pass | MIT | |
| CCPM Project Managementautomazeio/ccpm | 8.4k | — | ~1.1k | Automated safety check: Pass | MIT | |
| Cabloy Spec Generationcabloy/cabloy | 982 | — | ~3.2k | Automated safety check: Notes | MIT |
Similar skills
Shep Workstreams
shep-ai/shep
A skill your agent uses when a large body of work (a version milestone, an epic, a roadmap, a set of PRDs/design docs) needs to be broken into parallel workstreams and executed with the shep CLI.
Saga
warpdotdev/common-skills
Run an autonomous, spec-driven development "saga" for medium-to-large features using an orchestrator agent and a fleet of worker subagents.
CCPM Project Management
automazeio/ccpm
Runs a spec-driven workflow from PRD to epic to GitHub issues to parallel agents, with status, standup and blocked-work reports from bundled scripts.
Cabloy Spec Generation
cabloy/cabloy
A skill your agent uses to create or maintain Cabloy suite specifications under repo-specs, including PRD, SRS, PDP/WBS, acceptance planning, progress, and suite ADRs.
Project Planner
adrianpuiu/claude-skills-marketplace
Comprehensive project planning and documentation generator for software projects.
More from instructa/agent-skills
All 17 skills in this repoCodex Reviewer
instructa/agent-skills
Have Codex review a feature or change from Claude Code, then let Claude address the findings and request verification.
Search Context
instructa/agent-skills
Find, clone, inspect, and summarize high-quality GitHub reference repositories for coding agents.
Secleak Check
instructa/agent-skills
Run or install repo security leak checks with BetterLeaks and Trivy.
Delegate Fable
instructa/agent-skills
Delegate a bounded task from a Codex session to a Fable-powered Cursor Agent in the same Herdr workspace, then wait for and collect the result.
Delegate Grok
instructa/agent-skills
Delegate a bounded task from a Codex session to Grok 4.6 with xhigh reasoning in the same Herdr workspace, then wait for and collect the result.
Delegate Sol
instructa/agent-skills
Delegate a bounded task from a Codex session to GPT-5.6 Sol in the same Herdr workspace, then wait for and collect the result.
Related
Categories
Questions about App Spec Packager
What does App Spec Packager do?
A skill your agent uses when the user wants to turn an application, product, startup idea, SaaS, mobile app, web app, API, AI product, or internal tool into a production-ready Markdown specification…. App Spec Packager is an agent skill from instructa/agent-skills. Use this skill when the user wants to turn an application, product, startup idea, SaaS, mobile app, web app, API, AI product, or internal tool into a production-ready Markdown specification package for coding agents.
When should I use App Spec Packager?
App Spec Packager fits situations like: the user wants to turn an application; internal tool into a production-ready Markdown specification package for coding agents; simple one-off coding tasks unless the user asks for a complete spec; project plan for coding agents.
How do I install App Spec Packager in Claude Code?
Run `npx skills add instructa/agent-skills --skill app-spec-packager -a claude-code`. Or copy the skill folder (skills/specs/app-spec-packager in instructa/agent-skills) into .claude/skills/app-spec-packager in your project. Claude Code loads it when a task matches its description.
How do I install App Spec Packager in Codex?
Run `npx skills add instructa/agent-skills --skill app-spec-packager -a codex`. Or copy the skill folder (skills/specs/app-spec-packager in instructa/agent-skills) into .agents/skills/app-spec-packager in your project. Codex loads it when a task matches its description.
Can I use App Spec Packager in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add instructa/agent-skills --skill app-spec-packager -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/app-spec-packager, .gemini/skills/app-spec-packager, .github/skills/app-spec-packager and .opencode/skills/app-spec-packager in your project.
What does App Spec Packager need to run?
Going by SKILL.md and its folder, App Spec Packager needs Python for the scripts in its folder. Our summary lists: Python 3.
Does App Spec Packager access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is App Spec Packager safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does App Spec Packager use?
No licence was found for App Spec Packager or its repository. Without one, default copyright applies: ask the author before reusing or redistributing it.
How many tokens does App Spec Packager use?
About 1.5k tokens (SKILL.md is roughly 6.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 7.7k tokens, read only when the agent opens those files.
What are the alternatives to App Spec Packager?
Skills that share tags, products or a category with App Spec Packager: Schematic (blader/schematic, 240 stars), Shep Workstreams (shep-ai/shep, 264 stars), Saga (warpdotdev/common-skills, 608 stars) and CCPM Project Management (automazeio/ccpm, 8.4k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains App Spec Packager?
instructa (a GitHub organization) maintains it in instructa/agent-skills, which has 139 GitHub stars. The repository holds 17 skills in this directory. The repository was last updated on September 28, 2026.
Source: instructa/agent-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.