Grilling
Harness Wiki Refactor Grill Status
Harness Wiki Refactor Grill Status
Branch Dashboard
| Branch | Completion | Locked Direction | Open Items |
|---|---|---|---|
| Information Architecture | 100% | Move lifecycle flow navigation directly after Foundations; use Supported Flows as the reader-facing label while keeping the current routed Fumadocs architecture under apps/wiki/content/docs/**. | None. |
| Supported Flows | 100% | Lifecycle Flows focus on skill-flow and hybrid-flow usage: requirements, manual delivery, AFK delivery, runtime debugging, Review Current Branch, ClawPatch, and docs closeout. CLI adoption/setup/update move to Basic Usage and CLI docs with Harness value link-outs. | None. |
| Skill Guidance | 100% | Add skill-reference.mdx; cover the shared skill library by phase, agnostic, framework, and language groups in tables with Skill, Use when, Pack/category, and Source. | None. |
| Usage Overview | 100% | Expand get-started/basic-usage.mdx into the visible two-command workflow overview with post-setup handoff, sequence-style Mermaid diagram, backlog mapping, and a command/skill/hybrid capability table. | None. |
| Writing Shape | 100% | Preserve routed MDX style; expand Basic Usage, move command lifecycle pages into Get Started/CLI docs, reorder supported flows, add Review Current Branch, add Skill Reference, and revise flow openings. | None. |
| Entrypoint Architecture | 75% | Reframe the section currently labeled Supported Flows around available Harness entrypoints: phase flows, hybrid flows, and important atomic skills. Add an overview/index page that explains what HI can actually do. Remove /docs and /adopt sidebar shortcuts. Keep Get Started as-is. Move Foundations below the entrypoint section and make it more theory-forward. | Decide whether the public route/folder should stay lifecycle-flows with entrypoint language, or be renamed to an entrypoints route. |
| Page Consolidation | 80% | Merge trust-and-adoption into one page. Increase cross-linking to validation-and-tools. Link every tool mention to its wiki page when one exists, and every skill mention to the wearedevpunks/skills GitHub source page. | Decide exact route-retention/redirect policy if pages are merged or renamed. |
| Flow Title Semantics | 85% | Retitle flows around user intent: brainstorming/requirements/backlog definition, implementation delivery, debugging, review, massive bug hunt/fix, and docs update. Treat AFK delivery as a variant under the main delivery flow. | Decide whether these are title-only changes or file/url changes. |
Glossary
Terms
- Supported Flow: A documented operator-facing way to use Harness for a recurring work situation.
- Entrypoint: A documented way to start Harness work, including phase flows, hybrid tool flows, and important atomic skills.
- Backlog-Persisted Project Context: Project knowledge, context, decisions, glossary, accepted branches, and parked scope captured into backlog structure for future delivery.
- Phase Wrapper: A global orchestration skill that preserves workflow order, stop conditions, delegated inner skills, and validation evidence.
- Leaf Skill: A skill used inside a phase or local scope to do a specific slice of work.
- Skill Source Link: A GitHub viewer URL pointing to a source
SKILL.mdfile inwearedevpunks-skills. - Command Capability: A Harness capability invoked through the
dpCLI. - Skill Flow: A Harness capability invoked by the agent through a phase or workflow skill.
- External Tool Dependency: A tool or provider used inside a command, skill flow, or hybrid flow, such as ClawPatch,
agent-browser,opensrc,portless, Linear, or GitHub. - Hybrid Flow: A flow that combines command, skill, and external-tool behavior and should be labeled by its mixed nature instead of forced into one bucket.
Axioms
- Routed MDX under
apps/wiki/content/docs/**remains the canonical wiki content surface. wearedevpunks-skillsremains the reusable skill source of truth; synced.agents/skillsandapps/cli/skillscopies are mirrors.- Phase wrappers should be explained as wrapping inner skills, not replacing their contracts.
- First-run documentation must answer "so now what?" before sending readers into deeper methodology pages.
- Workflow diagrams should distinguish operator interaction, automatic steps, backlog/provider interaction, agent handoff, and external-tool reliance.
- External tools should be shown as dependencies inside command, skill-flow, or hybrid capabilities, not as standalone primary capability rows.
- A page that mentions a Harness tool or skill should help the reader jump to the owning reference, not leave discovery to sidebar hunting.
Flagged Ambiguities
- "repository graph" is rejected as canonical wording for the requirements flow. Use Backlog-Persisted Project Context or simpler prose around project knowledge/context persisted into backlog.
Parked Branches
- None.
Final Handoff
Information Architecture: 100%Supported Flows: 100%Skill Guidance: 100%Usage Overview: 100%Writing Shape: 100%Entrypoint Architecture: 75%Page Consolidation: 80%Flow Title Semantics: 85%
The original requirements grill was closed, then reopened by the 2026-06-27 public-surface refactor direction. Next direction: resolve route/rename semantics, then write and validate the wiki refactor.