file-followup

Spawns the architect agent to file a new package spec for an out-of-scope finding.

Updated Dec 27, 2025
One-click install
npx skills add https://github.com/HendrikGC02/Astroray --skill file-followup-hendrikgc02
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: file-followup
Source: https://github.com/HendrikGC02/Astroray/tree/main/.claude/skills/file-followup
Command: npx skills add https://github.com/HendrikGC02/Astroray --skill file-followup-hendrikgc02

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? During a work session, engineers often surface findings that are out of scope for the current package. This Skill captures those findings immediately by spawning the architect agent to file a new, tightly scoped package spec, so nothing gets lost between sessions. ## Core Features & Use Cases - Goal-capture pass: Invokes the architect agent in a brief mode that skips the dialogue phase and goes directly to writing the spec. - Lint-validated specs: Produces a new spec file at .astroray_plan/packages/<pkgNN>-<slug>.md that passes python scripts/project_index.py lint against TEMPLATE.md. - Auto-tagging and minimal diff: Tags the spec with Track: and limits the change to a one-PR doc update, leaving STATUS.md for round close. - Use Case: While working on pkg81, you discover that the accumulator resets on every camera pan. Run /file-followup accumulator resets per pan to have the architect file a new spec (like pkg83) scoped tightly to that finding. ## Quick Start Invoke /file-followup followed by a one-line reason describing the out-of-scope finding you want captured as a new package spec.

Frequently Asked Questions about file-followup

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I file a follow-up package spec for an out-of-scope finding?▼

Run /file-followup with a one-line reason describing the finding. The architect agent is spawned in a brief goal-capture pass and writes a new spec at .astroray_plan/packages/<pkgNN>-<slug>.md, skipping the usual dialogue phase.

What context should I pass when invoking file-followup?▼

Provide the one-line reason, the source context (which package discovered it, which PR, what the finding was), and the constraint that this is a follow-up spec rather than a strategy discussion.

Does the follow-up spec need to pass lint validation?▼

Yes. The generated spec must pass `python scripts/project_index.py lint` against TEMPLATE.md and be auto-tagged with a Track label before it is considered complete.

When should the architect skip the dialogue phase?▼

The architect skips dialogue and goes directly to writing the spec for follow-up filings, unless the scope of the finding is genuinely unclear and requires clarification.

Does file-followup update STATUS.md when filing a spec?▼

No. The output is a one-PR doc update containing only the new spec file. STATUS.md is updated separately at round close, not during the follow-up filing.