- name
SKILL.md
स्किल फ़ाइल पब्लिशर की रिपॉज़िटरी में ही रहती है।
कॉपी की गई कमांड टर्मिनल में पेस्ट करें। यह इस SKILL.md को उस एजेंट में इंस्टॉल करती है।
npx skills add phuryn/product-engineering --skill flight-deck -a cursor -yकॉपी की गई कमांड टर्मिनल में पेस्ट करें। यह इस SKILL.md को उस एजेंट में इंस्टॉल करती है।
npx skills add phuryn/product-engineering --skill flight-deck -a claude-code -yकॉपी की गई कमांड टर्मिनल में पेस्ट करें। यह इस SKILL.md को उस एजेंट में इंस्टॉल करती है।
npx skills add phuryn/product-engineering --skill flight-deck -a codex -yकॉपी की गई कमांड टर्मिनल में पेस्ट करें। यह इस SKILL.md को उस एजेंट में इंस्टॉल करती है।
npx skills add phuryn/product-engineering --skill flight-deck -a grok -yकॉपी किया गया संदेश Grok Bot चैट में भेजें। Bot यह SKILL.md GitHub से लाता है और उसे उन स्किल में जोड़ देता है जो आपके सभी Bot साझा करते हैं।
Install this skill: https://github.com/phuryn/product-engineering/tree/HEAD/agent-harness/skills/flight-deckपब्लिशर से
Write state down where it cannot be summarized. In a long session, tool output scrolls away and context becomes a plausible narrative with operational details sanded off. The work keeps running while your model of it goes stale. Then you re-run a paid job, report a number from memory, or forget that something is blocked.
The flight deck is STATUS.md, LOG.md and the owner's page. When the Artifact tool exists, build the page in the first pass as an artifact with a database (capabilities: {db: {}}). Use assets/owner-page.html, following references/owner-page.md; use OWNER.md only when the tool does not exist. A test run, or one with nothing for the owner to decide yet, still builds the page. It carries status too, and a test exercises it. A scheduled pass with no chat never builds or publishes a page; it checks the one its prompt names.
Rewrite STATUS.md in place to describe only what is true now. Never append to it, because a growing status file leaves the reader unsure which line is still true. Use these sections where they earn their place:
STATUS.md first. Reopening an old session is the fallback, because its memory is stale.Use the same sections for work that isn't code. references/other-work.md says how they map.
Append decisions and their reasoning to LOG.md, never rewrite its history. Include corrections and dead ends. Status answers "where are we"; the log answers "how did we get here, and what did we already rule out". Both are needed, in separate files.
Optionally commit a how-it-works doc when the machinery is non-obvious. Status and log are volatile; this durable doc belongs in version control and your routing file.
Give the owner a short status and only asks that need them. STATUS.md and LOG.md are for you. The page serves someone who isn't watching the session, so they never need the transcript to find the status or what you need. They open it, answer, save, and you read the answers at your next check-in. It makes STATUS.md's AWAITING section answerable. Without the Artifact tool, use OWNER.md with the same shape.
Keep a proposal's or plan's open decisions on the proposal's page. The owner's page links there and doesn't ask them; apply the propose skill, § 7.
Before building it, open references/owner-page.md (the data, publishing, the loop) and assets/owner-page.html (the page you copy).
A progress report starts here. Asked for "where we are", a status report, "what's done and what's next" or a progress deck, update STATUS.md and the owner's page first. Project the report from them; a deck is a view of the flight deck, never a separate account of the work.
Project a short status from STATUS.md, rather than every detail. A status block nobody reads to the end is no status.
references/owner-page.md for the data and migration.Delete the item and answer once you have read the answer. A gate stays until the go is typed in chat; a note on it deletes only the answer. Leave no reply on the page, no "settled" list, and nothing showing their feedback was processed. Work in this order:
STATUS.md QUEUED for work it creates, and LOG.md for the why, with the answer's id and at. An answer whose id and at LOG.md already holds is not recorded or queued again.Consume answers before acting, so answered items don't remain during work. Acting first leaves them on the page for as long as the work takes.
On a page with several areas, consume only your own area's answers. Other areas' answers wait on the page for their own sessions.
A run with no chat does steps 1 and 2 only. This scheduled pass does none of the work and never passes a gate. Put its confirmation in STATUS.md for the next session to repeat in chat.
Check at fixed points, because nothing notifies you when they save. Check at each stage boundary, while a build or review runs, before ending a turn, after a compaction, and whenever they say they answered.
An idle session with items waiting schedules its own check. Use a cron or loop where the harness has one, rather than waiting for the next message. For hours when no session runs, a scheduled headless pass checks instead (references/owner-page.md § A scheduled check without a session).
An answer given in chat closes its item too. A gate closes only when the answer is the go.
Make Save trustworthy. The page says Save is what you read and that nothing notifies you. On first use, quote one saved answer back. Put the link in every chat message that mentions the page.
Update STATUS.md on every state change. Do it when a job starts, finishes, fails or gets published, a decision lands, or something becomes blocked. Not "at the end", not "when asked": the moment it changes. A status file that is 80% true is worse than none, because it is trusted.
Keep status short enough to stay true. If maintaining it is a burden, it is too detailed.
Record measurements with their numbers and verdict, not the conclusion alone. The highest-value lines are probe results, benchmark numbers, verdicts, costs, and "we tested X and it does not work". Losing task state costs a re-read; losing evidence costs money and credibility. You might re-run a paid experiment or restate a number from a summary and get it wrong.
Keep one pair per area of work, not per repository. A repository with three unrelated efforts wants three pairs; three repositories serving one effort want one. The area is the unit someone would ask a status question about.
Keep files needed after a restart outside scratchpads and system temp. Status, logs, scripts, tools and cited evidence belong in the repository or another persistent working folder. Keep sensitive operator files uncommitted and protected there. Cross-link from the log to the status, and from long-lived docs to both, so a fresh reader can resume.
Read STATUS.md first, then skim the last few decisions in LOG.md. Verify that a process listed as running is actually running.
Do not trust the file over reality. Reconcile, then fix the file. A stale status caught early is a small problem. Trusting it blindly is how you report a job finished when it crashed an hour ago.
Skip this for short sessions, single-shot tasks and one-context-window work. The overhead is real and pointless there. Use it when a session will outlive its own memory. You can usually tell at the start from background jobs, queues, or a run measured in hours.
Each rule's origin, the case that taught it, is in receipts.md beside this file; read it when a rule's edge is unclear.
After a compaction, one read of the status board says what is running, what is blocked and on whom. Every line still matches what is on disk and what is running.
'What's the status', 'where were we', a progress report or status deck; long work that must survive compaction: multi-hour runs, background jobs, waiting on a decision.
---name: flight-deckdescription: 'What's the status', 'where were we', a progress report or status deck; long work that must survive…---# agent-harness/skills/flight-deck/SKILL.mdFAQ
पब्लिशर से agent-harness/skills/flight-deck/SKILL.md डाउनलोड करें, या पाथ कॉपी करके रिपॉज़िटरी खोलें। PlugMCP स्किल को सूचीबद्ध करता है, फ़ाइल होस्ट नहीं करता।
पब्लिशर इसे https://github.com/phuryn/product-engineering पर रखता है।
Claude, Cursor, Codex और Grok Build वह SKILL.md पढ़ सकते हैं जिसे आप पब्लिशर की रिपॉज़िटरी से जोड़ते हैं। जब आप चैट में स्किल के GitHub फ़ोल्डर का लिंक भेजते हैं, तो Grok Bot उसे इंस्टॉल कर देता है।